Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Solar
SFI 128
SN 113
A 18
K 2 Quiet
X-Ray C1.2
Wind 554.7 km/s
Aurora 3
Updated 22:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots
Select a band above to load spots
Ready — select a band to fetch live spots

using DXwatch and cluster apps together — am i doing this right?

 Loading...

so ive been playing around with a few different tools lately trying to figure out the best workflow for chasing DX and i honestly feel like im doing it the hard way. right now i have DXwatch open in a browser tab and then separately im running DX Toolkit on my phone and they dont always agree on whats being spotted which is kind of confusing when youre trying to work fast.

like the other day there was a spot for a 3B9 on 17m and it showed up on DXwatch maybe 2 minutes before it appeared in the app, so by the time i saw it on the phone and went to the rig the pile was already massive. is that just latency in the aggregation or is one of them pulling from different cluster nodes? i honestly dont fully understand how the spotting networks feed into these tools.

also been looking at DX Summit and QRZ's logbook DX spots and they seem to have yet another slightly different picture. does anyone have a setup they actually like for this or is it just kind of messy for everyone

  • Replies 1
  • Views 4
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah the latency thing is real and it basically comes down to which cluster nodes the tool is connecting to. DXwatch aggregates from a bunch of sources but there's still propagation delay through the network — not radio propagation, just the data hopping around between cluster nodes before it gets to the web interface. some spots have to touch 3 or 4 nodes before they end up on a site you can see.

what i do is run a direct telnet connection to a local cluster node in Ham Radio Deluxe or even just a raw telnet session when im actively hunting something specific. that gets you the raw spot stream with basically zero extra latency compared to a website that might be polling every 30 or 60 seconds. for casual browsing DXwatch is totally fine but when you need to move fast the direct connection makes a real difference. AR Cluster or CC Cluster nodes, whatever one is geographically close to you tends to be a bit snappier in my experience.

i had the same confusion when i first started trying to use these tools, there's just so many of them and nobody really explains how they relate to each other. the QRZ spot page is convenient if youre already on there looking up a callsign but i wouldnt rely on it as my primary for speed. honestly for just getting started i found DX Summit pretty straightforward and you can filter by band which helped me a lot when i was still figuring things out.

  • Guest unlocked, locked, unpinned and pinned this topic
  • Guest unlocked, locked, unpinned and pinned this topic
Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.