NTRIP diagnostics
Is this correction stream good?
Answer in five seconds, no receiver required. RTK Pulse connects to any NTRIP caster or mountpoint from your phone and tells you — in plain English — whether the stream is healthy, and what is wrong when it is not.
Honesty first: the test runs over this phone’s connection, not your receiver. Every verdict and exported report says so.
Three steps in the field
- 01
Enter the caster
Host, port, your NTRIP username and password. Or open a saved profile. Plaintext targets get an explicit “credentials sent in clear” warning.
- 02
Pick a mountpoint
The live SOURCETABLE is fetched from the caster and sorted by distance from you. Network-RTK mountpoints (VRS/MAC/FKP) are detected and handled.
- 03
Read the verdict
A sentence you can act on, four stat cards for the detail, and a diagnostic ladder — host, port, credentials, stream quality — when the test fails.
What it actually checks
A dedicated NTRIP and RTCM3 decoder that reads the actual message stream — not a wrapper around a generic client — packaged as a single-user diagnostic.
Plain-English diagnosis
Not a hex dump. A sentence that names the failing rung: unreachable host, wrong port, rejected credentials, or a stream that connects but never sends corrections.
RTCM message breakdown
Which message types arrive, at what rate, and whether the set is complete enough for a fix — including the base/VRS station message.
Latency and arrival age
Correction age percentiles over the run, not a single lucky sample — so an intermittently stalling stream cannot hide behind an average.
Signal, satellite by satellite
Per-constellation C/N₀ — min, mean and max — plus every satellite the base broadcasts and its strongest signal on each frequency band, so a weak or single-frequency base cannot hide.
Ready for RTK, or not
Beyond “bytes arrive”: a dual-frequency suitability verdict, cycle-slip continuity and MSM level — the health checks that decide whether a receiver can actually resolve a fix.
Network-RTK aware
For nmea=1 mountpoints the app injects the GGA position the protocol requires, then reports whether the network actually answered with a virtual station.
NTRIP v1, v2 and TLS
Both framings, plus TLS on 443/2102 with strict certificate validation. Local bases on your own network are fair game too.
A report you can send
Export a timestamped PDF of what the stream did, so a support ticket starts with evidence instead of “it doesn’t work”. It carries your NTRIP username so support can find the account — never your password — and your position only if you switch it on.
What it costs
Nothing. Every feature works without an account — testing, the test details, history, the PDF report, the map. Signing in adds one thing: a backup of your profiles and history, so a new phone gets them back.
| Test any NTRIP connection | Unlimited |
|---|---|
| Plain-English diagnosis | Included |
| Test details — tests, summary, health, messages, satellites | Included |
| Saved profiles | Unlimited, on the device |
| Session history | Last 50 runs, on the device |
| Repeat a past test in one tap | Included |
| Export the PDF report, or copy it as text | Included |
| Mountpoint map | Included |
| Backup and restore of profiles and history | Sign in — free |
No subscription, no in-app purchases, no sign-in wall. The account is optional and adds backup and restore: the server keeps one copy per account — whichever device saved last — and puts it back when you sign in on a new phone. That is not live sync between two phones in active use, and the test details stay on the device that recorded them.
Where your data goes — and where it does not
Your NTRIP passwords stay on the device, in the platform keystore. They leave it only toward the caster you asked us to test — never to our servers, not even with an account.
Connecting to a network-RTK (VRS) mountpoint sends your position to that caster operator, because the protocol requires it. We ask before the first run, we say who receives it, and by default we round the position to about a kilometre before sending it.
In development
RTK Pulse is being built for iOS and Android. If you run RTK in the field and want an early build, leave us your contact — we come back with a beta invite, and we are glad to hear which network you use and which phone you are on.