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 201
SN 126
A 14
K 1 Quiet
X-Ray C4.3
Wind 398.1 km/s
Aurora 1
Updated 11:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Good 12/10m Good
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

confused about DXwatch vs cluster spots on QRZ — whats the difference really

 Loading...

ok so ive been licensed about 8 months now and im starting to get into DX chasing a little bit. i keep seeing people mention DXwatch and then also QRZ has that spot thing built into the logbook and i honestly cant figure out if theyre pulling from the same data or what. like sometimes ill see a spot on DXwatch and then check QRZ and its not there yet, or vice versa.

also someone in my local club mentioned using a dedicated cluster client, i think they said DX4WIN or maybe it was something else, and connecting directly to a telnet cluster node. is that actually better than just using the web stuff? feels like a lot of setup for something i can just open in a browser. im probably missing something obvious here. running mostly HF, TS-590SG if that matters, just getting into chasing DX on 17 and 20m mostly.

  • Replies 1
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah so they're related but not exactly the same thing. DXwatch aggregates spots from a bunch of different cluster nodes and displays them in a nice web interface, QRZ has their own spot feed too but i think they filter or deduplicate differently so you'll see some timing differences. neither is "wrong" they just grab from different parts of the cluster network at slightly different times.

the telnet thing your club guy was talking about is connecting directly to a DX cluster node like ve7cc or one of the big ones. the advantage is you get spots the instant they hit that node, no web layer in between adding latency, and you can set filters so you only see bands you care about or exclude spotted stations you already have confirmed. for casual DX chasing the browser tools are totally fine honestly. i used DXwatch for probably two years before i bothered with a direct client. once you start getting more serious about chasing a specific entity or working contests it starts to matter more.

i was in the same boat not too long ago, the whole cluster ecosystem is kind of confusing when you first look at it. one thing i started doing was just keeping DXwatch open in a tab while im on the radio and it works pretty well for 20m hunting. the color coding by band is nice once you figure out what youre looking at.

one thing nobody told me that would have saved some frustration — make sure you set your home callsign in whatever tool you use because some of them will highlight spots that are "new" for you based on your log if you connect it up. QRZ does this if you sync your logbook. kinda cool when it starts flagging stuff you still need.

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.