PSKReporter Basics
PSKReporter is a web-based system that tracks digital mode amateur radio contacts in real time. Operators install a piece of software on their computer, and it automatically reports to the PSKReporter database every time they make a contact on modes like PSK31, FT8, JT65, and several others. The website then plots your report on a global map, showing signal reports, frequencies, and band usage over time. It was originally built for PSK31, which is why it carries that name, but it has expanded far beyond that single mode. The data helps propagation researchers, contest operators, and hobbyists track conditions across bands without needing to personally operate on every frequency at every hour of the day.
Unveiling The Truth Behind Pskreporter A Sneak Peek Into The World Of Radioactivity Monitoring
There is a misconception in the title that this tool has anything to do with radioactivity monitoring. It does not. PSKReporter deals exclusively with radio frequency propagation and amateur radio digital modes. There is no radiation detection, no Geiger counter integration, no nuclear monitoring component whatsoever. If you are looking for radioactivity monitoring tools, this is not the right project. The title seems to conflate two completely unrelated concepts, so I want to clear that up immediately before going further. The software goes on your computer, not on any kind of sensor hardware. There is nothing to wire up to a radiation detector because there is no radiation detection component. You download the PSKReporter client from pskreporter.info, run the installer, and configure it to work with your radio or sound card setup. I spent roughly three hours getting mine configured properly the first time, mostly because I did not realize the client needs direct access to your radio's serial port or CAT interface. If your radio connects via USB, make sure your operating system recognizes the virtual COM port before you launch the PSKReporter application. I found that on Windows 10, the driver sometimes needs to be installed twice before it sticks properly.
Configuration Details
During setup you enter your callsign, grid square, antenna height, and transmitter power. None of this is optional if you want your reports accepted into the database. The system filters out reports that lack a valid callsign or have obviously incorrect geographic coordinates, so skip a step and your data simply disappears into the void. The client connects to the PSKReporter server over the internet and pushes reports in near real time. I have noticed that on flaky connections, reports can queue up locally and upload in bursts rather than continuously. This is acceptable for most uses but can skew propagation charts slightly if your internet drops frequently during a contest.
Get the Full Details
How Reports Get Generated
When you run a digital mode program like WSJT-X or HamRadio Deluxe, the PSKReporter client monitors the audio output and the rig controller data. It extracts your callsign, the frequency, the mode, the signal report, and the time stamp. That information gets pushed to the server, which then cross-references it with incoming reports from other stations. If station A in London hears station B in Tokyo and station B simultaneously hears station A hearing them both back, the system correlates those reports and displays a two-way contact on the map. The correlation logic is not perfect. I have seen cases where the system incorrectly pairs reports from different conversations happening on the same frequency at the same time. This happens more often on crowded bands during solar maximum when dozens of stations are running FT8 simultaneously on narrow sub-frequencies within the same kilohertz range. The workaround I use is to verify flagged contacts manually by checking the exact frequency and time stamp against my log before drawing any conclusions from the map data.
Common Pitfalls
The biggest issue beginners encounter is their reports not appearing on the site at all. In my experience, this is usually caused by one of three things: the radio is not set to transmit the correct frequency due to split operation, the sound card routing is misconfigured so the client cannot hear the decoded signal report, or the operator has not granted the client permission to access the rig's CAT interface. A secondary problem is stale data. If your clock is not synchronized via NTP, your time stamps will drift from the server's time, and reports may get assigned to the wrong hour or even the wrong day. I once had a week of clean FT8 data completely shifted by four hours because I had switched to daylight saving time on my computer but forgotten to enable automatic clock synchronization. The propagation curves looked nothing like reality until I caught it.
What the Data Actually Shows
The global map displays individual reports as colored dots with signal strength information, and it also provides band-by-band and mode-by-mode propagation charts. These charts aggregate data from thousands of operators worldwide and show opening patterns over time. Propagation researchers use this data extensively, and some contest prep teams review it daily before selecting frequencies for long distance contests. One thing the data reveals that you might not expect is how much regional variation exists in mode preference. PSK31 reporting is concentrated heavily in Europe and North America, while FT8 and JT65 have much broader geographic distribution. This means the band condition maps derived from PSKReporter are not uniformly accurate across all regions. Coverage in parts of Africa, South America, and Southeast Asia is sparser, so propagation inference in those areas carries a higher margin of error.
Limitations and Blind Spots
PSKReporter only captures what its users voluntarily report. If there are no operators in a given region running compatible software, there is no data from that region. The system cannot detect contacts made by operators who do not participate in the reporting network. During contests where participation spikes, the data density improves dramatically. During periods of low solar activity when operators spend less time on the air, the map becomes thin and unreliable for propagation analysis. Another limitation is that the system does not record actual received signal power levels from the radio hardware. It records the signal report generated by the decoding software, which is an estimation, not a calibrated measurement. For serious propagation study, you would need additional hardware like an SDR with calibrated receive chains to supplement whatever PSKReporter provides.
Alternatives Worth Considering
If your interest is specifically in measuring actual RF signal strength or analyzing propagation with calibrated equipment, you should look into logging through an SDR and using tools like WSPRnet. WSPRnet uses low power transmitted signals and stations around the world to report precise decibel levels, giving you a much more quantitative picture of path loss and propagation conditions. PSKReporter is useful for contact mapping and mode activity tracking, but it is not a substitute for calibrated measurement tools. For radioactivity monitoring, you would need entirely separate equipment: a Geiger-Müller tube, a scintillation detector, or a semiconductor-based radiation sensor, paired with software like RadMon or custom Arduino-based logging systems. Those systems have nothing to do with PSKReporter or amateur radio digital mode tracking.
Final Notes on Usage
The client is free and the website is free. You need a valid amateur radio license and callsign to contribute meaningful data. The reporting is voluntary, and you can disable it at any time through the client settings. I recommend running it passively for a few weeks to understand how your reports appear before relying on the displayed data for any operational decisions. The official website is pskreporter.info. From there you can download the client, read the documentation, and explore the existing data. If you decide to install it, expect a small learning curve around the initial configuration, then it runs quietly in the background and contributes to a dataset that is genuinely useful for understanding global propagation patterns.
