CW Skimmer and Automated Morse Decoding: How the Reverse Beacon Network Works

The Software That Listens to an Entire CW Band at Once

A human CW operator, no matter how skilled, can only really copy one signal at a time. CW Skimmer and the Reverse Beacon Network (RBN) built on top of it solve a different problem entirely: decoding dozens of simultaneous Morse signals spread across an entire band segment, automatically, in real time, and reporting what was heard to a global database anyone can query. This guide covers how that technology actually works, what it’s genuinely useful for, and where its output fits alongside the DX cluster spotting most operators are already familiar with.

If you haven’t read our overview of DX cluster spotting and etiquette, it’s a useful companion piece — RBN spots and traditional human cluster spots increasingly flow through the same tools and displays, even though they’re generated in completely different ways.

How CW Skimmer Actually Decodes Multiple Signals at Once

A conventional CW decoder works the way a human ear does: it locks onto one frequency, follows the on/off keying pattern, and outputs decoded text for that single signal. CW Skimmer, created by Alex Shovkoplyas (VE3NEA), takes a fundamentally different approach: it processes a wide slice of spectrum — as much as an entire band segment, depending on the receiver feeding it — through a Fast Fourier Transform, converting the incoming RF into a detailed waterfall of energy across frequency and time. From that wideband picture, the software identifies every distinct CW signal present, tracks each one’s keying pattern independently, and decodes all of them in parallel rather than one at a time.

This is only possible because of two things arriving together: software-defined receivers capable of digitizing a wide enough slice of spectrum to feed the FFT pipeline, and enough processing power on an ordinary PC to run that many parallel decoders in real time. Older single-signal CW decoders didn’t disappear because the algorithm changed — they were simply solving a narrower problem than what a wideband SDR and modern CPU now make practical.

From a Single Skimmer to a Global Network

A single CW Skimmer installation, watching one band from one location, is already a useful local tool. The Reverse Beacon Network turns that into something much bigger: a worldwide, volunteer-run network of skimmer stations, each one running the decoding software against its own receiver and continuously uploading everything it hears to a central aggregation system. Query the Reverse Beacon Network for a specific callsign or band, and you’re seeing a real-time aggregation of what dozens or hundreds of independent receiving stations around the world are actually copying, each one automatically, each one unbiased by human attention or interest in that particular signal.

This is the property that makes RBN data different in character from traditional DX cluster spots: a cluster spot reflects one human operator noticing a signal and deciding it was worth sharing, while an RBN spot reflects an automated receiver simply reporting whatever it decoded, regardless of whether anyone finds that particular station interesting. Both kinds of data end up flowing into many of the same aggregated spotting displays and alerting tools today, but they’re generated by fundamentally different processes with different biases.

What RBN Data Is Actually Useful For

Self-Spotting and Signal Reach Verification

Calling CQ and checking RBN a moment later tells you, with real objectivity, how far your signal is actually being heard and how strong it’s arriving — a far more concrete answer than guessing from the pileup you do or don’t get. This is popular during contests and DXpeditions specifically because it removes the guesswork about whether a quiet band segment means nobody’s listening or nobody can hear you.

Real-Time Propagation and Band-Opening Detection

Because skimmer stations run continuously and report everything they copy, a sudden cluster of RBN spots between two regions that weren’t hearing each other minutes earlier is a genuinely useful, near-instant signal that a band has opened along that path — often faster and more concretely than a propagation prediction model can tell you, since it’s reporting an opening that’s actually happening rather than one that’s merely likely.

Contest Log Checking and UBN-Style Analysis

Because RBN records include timestamp, frequency, and often signal strength for huge numbers of contest-period CW contacts, contest sponsors and serious log-checkers increasingly cross-reference submitted logs against RBN data as one input into busted-callsign and off-frequency analysis — a complement to, not a replacement for, the traditional UBN process based on comparing logs against each other.

Integrating RBN Into Your Station Software

Most modern contest logging software can connect directly to RBN’s telnet feed the same way it connects to a traditional DX cluster, pulling in real-time skimmer spots alongside human-posted cluster spots in the same bandmap or spot window. This is one of the more practical everyday uses of RBN data: rather than manually checking a website, a contester running a program like N1MM+ or one of the other major loggers covered in our contest logger comparison sees RBN-sourced spots appear automatically in the same interface used for regular operating, often filterable separately from human spots since the two carry different reliability characteristics for different purposes.

Because RBN spots are generated automatically rather than by a human deciding a station is worth sharing, they tend to include a much larger volume of routine, non-rare stations than a traditional cluster feed. Most operators apply filtering — by band, by minimum signal strength, or by excluding stations already worked — to keep the resulting spot flow useful rather than overwhelming, the same filtering discipline covered in more general terms in our piece on DX cluster etiquette and filtering.

From a Manual Curiosity to Infrastructure

RBN grew out of a fairly narrow original use case — CW Skimmer users sharing their decoded spots with each other informally — into infrastructure that a meaningful part of the contesting and DXing world now depends on without necessarily thinking about it directly. Propagation study, contest strategy, DXpedition pileup management, and even some academic ionospheric research have all made use of the large, continuously growing dataset RBN produces simply as a byproduct of its core spotting function. That evolution is worth knowing about mainly because it explains why RBN today feels less like a hobbyist side project and more like shared infrastructure maintained by a distributed volunteer network — which also means its continued usefulness depends on volunteers continuing to run and maintain skimmer stations, the same way any other community-maintained resource does.

Running Your Own Skimmer Node

Contributing a skimmer station to RBN requires a wideband-capable SDR receiver, a reasonably quiet receiving location and antenna, a PC with enough processing headroom to run the decoding software against your full monitored bandwidth continuously, and a stable internet connection to upload results. It’s a genuinely approachable weekend project for an operator who already owns a suitable SDR for other purposes, and it contributes real value back to the community rather than only consuming RBN’s aggregated data — every additional well-placed skimmer improves the network’s overall coverage and the propagation picture available to everyone using it.

Before setting one up, check the specific software’s current documentation for supported receiver hardware and bandwidth requirements — this is exactly the kind of detail that changes as new SDR hardware becomes available, and a guide written even a couple of years ago may understate what’s now practical on a modern low-cost SDR.

Limitations Worth Knowing

• Coverage isn’t uniform. RBN’s usefulness for any specific path depends entirely on whether a skimmer station happens to be positioned to hear it — dense in some regions, sparse in others.
• It only covers modes it can decode. CW and RTTY are the traditional strongholds; it doesn’t replace mode-specific tools like PSK Reporter for FT8 and other digital modes.
• A strong RBN spot doesn’t guarantee a usable path for you specifically. A skimmer station with an excellent antenna at a quiet location may hear something your own more modest station won’t, and vice versa.
• It’s a real-time snapshot, not a forecast. RBN tells you what’s being heard right now; for looking ahead, propagation prediction tools remain the better tool for planning rather than reacting.
• Historical data has practical limits too. While RBN does retain historical spot data that’s genuinely useful for after-the-fact analysis of a contest or an opening, it’s a record of what was heard, not a substitute for a proper propagation model when planning a future operating session.

Frequently Asked Questions

Is CW Skimmer the same thing as the Reverse Beacon Network?

No. CW Skimmer is the decoding software that runs at an individual receiving station; RBN is the global network and database that aggregates spots from many independent skimmer stations running that software (or compatible alternatives) around the world.

Do I need to know Morse code myself to use RBN data?

No. RBN’s entire value is that the decoding happens automatically — you can use the spotted callsign, frequency, and signal data without personally copying a single dit or dah.

Can RBN spot me without my knowledge or consent?

Yes, if your CW signal is within range of an active skimmer station, it will typically be decoded and reported automatically like any other CW signal on the band — there’s no opt-out mechanism, since skimmer stations simply report whatever they receive.

Does using RBN for self-spotting count as legitimate operating, or is it considered cheating?

Rules vary by contest and event, and some competitions restrict or prohibit self-spotting through any means, RBN included. Check your specific contest’s current rules before relying on RBN-based self-spotting as part of your operating strategy.

Why do some of my contacts show up on RBN and others don’t?

Coverage depends on whether an active skimmer station happened to be tuned to and within range of your specific frequency at that moment — it’s not a complete record of everything transmitted on a band, only what the current network of skimmer stations actually captured.

Is running a skimmer station expensive?

Not especially, if you already own a wideband SDR receiver for other purposes. The main ongoing cost is a dedicated or shared PC with enough processing capacity and a stable internet connection, rather than any specialized additional hardware.

Does RBN work for SSB or FM voice signals?

RBN’s core decoding technology is built around CW, with RTTY support added over time; it isn’t designed to decode voice modes the way it decodes Morse. Voice and other digital modes each have their own separate automated spotting ecosystems, such as PSK Reporter for many digital modes, rather than being folded into RBN itself.

The Bottom Line

CW Skimmer and the Reverse Beacon Network turned a fundamentally single-signal technology — CW decoding — into a wideband, automated, global monitoring system, and in doing so created a genuinely different and complementary data source to traditional human DX spotting. Whether you’re using it to check your own signal’s reach, catch a band opening in real time, or just understand where the spots showing up in your favorite cluster display are actually coming from, it’s worth knowing it’s not the same process as a human operator noticing your CQ and deciding to share it.