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
The same NTRIP/RTCM3 engine that powers fixcast, our caster-operator monitoring product — 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 PDF that proves what the stream did. It carries your NTRIP username so support can find the account — never your password — and your position only if you switch it on.
Free and Pro
Testing is unlimited and free, with no sign-in wall. Pro is for proving a failure was the caster’s fault, and for watching a stream over time.
| Free and Pro | Free | Pro |
|---|---|---|
| Test any NTRIP connection | Unlimited | Unlimited |
| Plain-English diagnosis | Yes | Yes |
| Full log — tests, summary, health, messages, satellites | Yes | Yes |
| Saved profiles | 2 | 5 |
| Session history | Last 3 | Unlimited |
| Repeat a past test in one tap | — | Yes |
| Account data | Encrypted backup & restore | Live multi-device sync soon |
| Export diagnostic PDF report | Copy as text | Unlimited |
| Share report link | — | Soon |
| Stream quality alerts | — | Soon |
| Smart mountpoint map | — | Soon |
Pro is a subscription bought through the App Store or Google Play; the price and period are shown in the app at purchase time. Buying it asks you to sign in first, so the subscription follows you to a new phone. Working without an account stays a first-class mode — diagnostics, two profiles and recent history all work offline.
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.