EU e-Privacy Directive

This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

View e-Privacy Directive Documents

You have declined cookies. This decision can be reversed.

Are you unsure about which DX Cluster node suits you best? Have you tried several nodes only to be greeted with the dreaded "Connection failed"? If the answer to either question is "yes" do not despair - try one of the nodes below with its status listed as "Success"!

Please see the notes below for details about the limitations of this tool.

Node Host name Port Type Status Last Reported Reports

When using this tool, please note:

  • This table is generated by trying to connect to each listed node from a network hosted in United Kingdom. Depending on your local ISP's connectivity, you may find you are able to connect to nodes that aren't reachable from a network this test has run on (and, conversely, you may not be able to connect to all the hosts listed as "Success").
  • This table represents a snapshot in time, currently updated every 6 hours (see the Last Reported column). A node listed as "Success" may not necessarily be available when you try to connect to it. Conversely, a node listed as "Failed" may have meanwhile gone online.
  • The above table comprises the nodes listed in Telnet Directory on www.dxcluster.info. If your node isn't listed, please contact the owner of this site and arrange that it gets added. Please also use the opportunity to thank him for this excellent and very valuable resource!

NKCCluster version 2.1.1 has been released on Sunday, 11th October 2015.

It delivers two improvements related to callbook handling:

  • Further to feedback from users who don't use XML callbook access, it now opens a full-screen browser window neatly integrated with the rest of the application.
  • Support for QRZ.com XML access

Please note QRZ.com XML access is only available to NKCCluster donors with valid QRZ.com XML subscription.

I enjoy taking part in ASISS SSTV events. To receive a signal from the International Space Station no advanced azimuth-elevation rotators or low-noise preamplifiers are required, although they certainly do help those who have them.

In January 2015 I finally felt brave enough to try to receive one such broadcast for the first time ever. Frequency... checked. Recording... checked. Tracking software... checked... I can literally feel my heart starting to beat faster. White noise... Nothing... Maximum elevation, still nothing. I'm checking the RX frequency again, it should be fine. Suddenly I can hear a warbling signal. That's it, my first ham signal from space!

As it turned out, the time of maximum elevation at my QTH corresponded with the 3-minute break the ISS guys make in-between two pictures, so I managed to receive only something at the end of my pass. Still, an image from space!

Even with this modest setup (just a simple fixed dipole in the loft + FT857D) I managed to receive my first image from space. Partial decode and noisy but a signal from space nevertheless.


And this was enough to get me hooked. I soon realised the ability to track a satellite was more important than the receiver specs. My next attempt, in February 2015, was done using just a Yaesu VX-7R handheld, while sitting in my car and enjoying my lunch break. This time I got really lucky: 2 full decodes!


But my by far most exciting experience so far happened this April. Using a handheld 2m dipole and my FT857d this time around I managed to hear the end of one image and just as I started cursing my luck suddenly a male voice with Russian accent called other stations. I couldn't believe my ears, I was actually hearing a real astronaut! Hear for yourself (fast forward to about 4:20 minutes if it doesn't happen automatically).

In all this excitement by the time I managed to google the ISS uplink frequencies the pass was already over. But this got me even more motivated to be there for RS0ISS next time around.



A new NKCCluster release has been released via Google Play on Friday, 31st July.

The focus in this release was usability. Based on users' feedback the application has been de-cluttered and simplified.

Configuration Wizard

Configuration Wizard now uses a simple tabbed interface, where a swipe to the left brings the user to a previous step and a swipe to the right to a next one and thus ensures essential information gets captured with minimal inconvenience.


Spots and Notifications

Spots are now more readable, with fonts that scale depending on screen size.

Notifications are now displayed in the same screen as spots, thus becoming immediately visible as soon as they are received.



Filters have been moved away from main screen and now exist as a separate menu that opens by touching the icon in the upper left-hand corner or dragging the left edge of the application to the right.

In the "Filters" menu there is one simple switch that enables or disables the filters. Disabling the filters results with all received spots being shown.


Better use of screen area

Instead of wasteful and unsightly large blank areas taking up half a horizontal space both in portrait and landscape, this area is now used for showing the details of a selected spot. On small screens this area can be extended or retracted by dragging it to the left or right of the screen.


XML Lookups

Note: this feature applies only to hamqth.com lookups, users who use other callbooks will still get a browser window with a callbook link open.

The results of the XML lookups are now neatly presented. E-mail or Web links (if given) are also clickable, thus making it possible to email the operator without leaving NKCCluster.


New translations

Thanks to sterling efforts of EA4TV and RZ3EM, NKCCluster is now available in Spanish and Russian languages respectively.


For normal operation NKCCluster requires the following permissions:

This permission is required for GPS Locator.

Recommended for Google Maps API v2 (used in GPS Locator) but not actively in use.

This one is pretty self-explanatory, isn't it? Without network access NKCCluster wouldn't be of much use.

Required for Google Maps API v2 (used in GPS Locator).

Required for Google services (Maps and Billing).

Required for spots' notifications.

Cluster nodes in general don't cope well with user sessions switching from one network to another (for example WiFi to 3G or vice-versa). This permission is required to detect when a network a device is connected to changes (or becomes unavailable) and take appropriate actions.

Required for Google Maps API v2 (used in GPS Locator).