Your first CW session

Choose. Tune. Make contact.

Start with your station and a small set of spotters. Refine the filters after you have seen some activity.

Let CW Hunter do the cross-checking

If your usual routine is to find an active CW callsign on POTA.app or WWFF.co and then check its reception at a nearby RBN station, this app automates those steps. It matches current activations with your chosen spotters and alerts you to promising QSO opportunities while the monitor is open.

The Reverse Beacon Network (RBN) is a network of listening stations, or spotters, that report the stations they hear, the frequency, time and signal strength. Choose spotters near your QTH to make those reports useful for your own hunting. Nearby reception is a useful indication; your antenna and local conditions also matter.

1. Set your station

Open the menu → Settings. Enter your operator callsign for QSO logging. Add your home Maidenhead locator for distance, bearing and nearby spotter search. Location is optional. You can enter it manually, request approximate location or request GPS when supported.

2. Select your spotters

In the spotter selector, choose a DXCC entity or search for nearby spotters using your QTH. Review each spotter’s locator, distance and bearing. Select up to five.

Use spotters replaces the current list; Add spotters adds your selection to it, within the five-spotter limit.

3. Follow the activation list

POTA and WWFF activations are checked against RBN receptions at your selected spotters. New entries stand out in ACTIVE. Older or inactive entries remain in HISTORY for the configured retention period.

Tap a row to see the reference name, QTH, distance, bearing and elapsed First/Last times. Reference links open the relevant program website. A different RBN frequency is shown separately when available.

Higher dB means stronger reception at that spotter. RBN reports describe another antenna and location, not a measurement of your own receiver.

4. Adjust filters and sorting

Use the list’s Filters control to select bands and spotters or set lower and upper dB limits. You can use either limit alone or both together. Per-band limits override general limits only for enabled bands.

Use Sort to order activity by recent or first detection, frequency, signal strength, WPM or distance.

5. Enable Morse alerts

In Settings → Alerts, choose whether to play a program letter, a callsign or a full CQ announcement, and which new entries to announce. Adjust character speed, Farnsworth spacing, pitch and pauses. Use Test Morse and check your phone’s selected audio output and volume.

The optional playback panel highlights the current character. Tap it to stop playback. Tap the new-entry banner to acknowledge the notification. Keep screen on prevents automatic screen dimming; monitoring pauses when the app is no longer visible.

6. Follow your callsign watchlist

Add callsigns, names and a short comment under Callsign watchlist, or import a Friends CSV. The Watchlist alerts switches in Programs & timing and on the watchlist page control the same setting; disabling alerts keeps the list. When enabled, a Friend heard by your spotters gets a distinct alert and a CQ callsign announcement, independently of the activation programs.

7. Log and export a QSO

Expand the activation and mark QSO completed after making the contact. Review the log details before saving. Completed entries move to HISTORY and get a visible completion mark.

Open Completed QSO log or Export completed QSOs (ADI) from the menu. Incremental export starts after the previous export; adjust the date range when needed. Save the ADI file through Android’s file picker. Event and daily CSV exports are separate from completed-QSO ADI exports.

Optional QRZ operator details

QRZ is not required for monitoring. Open Settings → QRZ.com to sign in with your own account. Saved credentials are encrypted on the device if you choose Remember login; otherwise they last only for the app process. Operator lookups happen when details are expanded.

Without login, the app explains how to sign in and still offers the browser link. A rejected or expired login is shown separately from a connection failure. Portable calls can fall back to their base callsign when QRZ explicitly reports the full call as not found.

SOTA and the Python monitor

SOTA data is imported from a local JSON file; there is no direct SOTA API connection. The companion Python application runs separately in a Linux terminal and can read Friends from CSV. Android and Python do not automatically synchronize settings or databases.

Version and licenses

The last entry in Settings, About, shows the installed version and versionCode, UTC build date, copyright and application website. Application and third-party licenses are available there without an internet connection.

← Back to the app overview