multimon-ng
1.6.0 open-sourceThe section your link pointed to isn't on multimon-ng's page any more, so we've brought you to the top.
Multimon-ng decodes and displays digital radio signals including POCSAG, DTMF, and other modes from audio input or SDR receivers.
rtl_fm -f 929612500 -s 22050 | multimon-ng -t raw -a GSC -a FLEX_NEXT /dev/stdin gen-ng -P "Test page message" -A 1234567 -B 1200 -t raw - | multimon-ng -t raw -a POCSAG1200 - flac -d --stdout ~/recordings/rtlfm.1725033204.flac | multimon-ng -r -v 0 -a FLEX_NEXT -t flac - rtl_fm -f 929.0125M -s 22050 | multimon-ng -t raw -a FLEX --flex-no-ts - multimon-ng -a POCSAG -f auto input.raw
Summary
multimon-ng is an open-source command-line decoder for digital radio transmission modes, taking audio from a live feed or raw samples piped in from tools like rtl_fm or sox and decoding formats such as POCSAG, FLEX, EAS, AFSK, DTMF, GSC, and Morse. It's built for people working directly with SDR hardware and captured signal data, such as radio hobbyists and researchers monitoring paging and public-safety traffic, rather than for general network security teams. It runs on Linux, macOS, Windows, and FreeBSD, and can output structured JSON or timestamped logs for feeding into a separate analysis pipeline. As the successor to the original multimon, it fills a fairly specific niche and isn't positioned by its README against any named alternative. Development is active: 56 contributors, 44 commits and 15 releases in the past year, with the last release only 25 days old.
Multimon-ng decodes and displays digital radio signals including POCSAG, DTMF, and other modes from audio input or SDR receivers.
How multimon-ng helps
What is actually being transmitted on this frequency I'm capturing?
listens to the demodulated audio stream and decodes it against the supported modes (POCSAG, FLEX, EAS, AFSK, DTMF, Morse, and others), printing the recovered messages as they arrive
Which pager messages went out over this capture, and can I feed them into something else?
reconstructs paging traffic from POCSAG, FLEX, and GSC streams, correcting errors as it decodes, and can emit that as structured JSON instead of plain text for a downstream pipeline to parse
Can I tell exactly when each decoded message came in, in a way that lines up across time zones?
tags each decoded line with a timestamp, with an option to use UTC ISO-8601 form so logs from different sites or runs stay comparable
Is my SDR setup and antenna actually working before I go monitor something live?
generates POCSAG and FLEX test tones that can be fed back into the decoder or another receiver to confirm the chain decodes correctly before relying on it
Was that recorded capture from a paging channel worth digging through, or is it silence and noise?
replays a recorded audio file (WAV, FLAC, or raw) through the same decoders used for live input and prints whatever valid messages it finds, so a capture can be triaged after the fact
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for multimon-ng, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail multimon-ng puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
4 entries
No entries match these filters.
- July 20261
- February 20251
- September 20201
- July 20191
Project health
Issue, contributor and maintainer activity in EliasOenal/multimon-ng, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 7 +5 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 67 days first maintainer reply 29 days
- Open backlog 65 of 160 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 65
- Contributors / month 1
- Commits / month 2
- Stars 1,137
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.