NTRIP Client
Connect to a GNSS correction caster and turn the stream into a position — a live single-point solution, a centimetre-level RTK baseline, or a recorded RINEX file. Browse the sourcetable on a map and pick a mountpoint to begin.
Just want to see what's inside the stream — message types, rates, decoded fields? Use the Stream Inspector instead; it reads NTRIP, raw TCP and USB receivers.
Connections are proxied through a minimal relay that forwards data without storing it. Your credentials are sent directly to the caster — nothing is logged or retained.
How It Works
- Enter a caster address and click Get Sourcetable to list available streams.
- Click any mountpoint to connect — look for the icon next to each stream.
- The live monitor shows message types, satellite C/N0, sky plot, and station metadata.
- Hit Record RINEX to capture observations and download a .obs file.
Network-RTK / VRS position (optional)
Live RTK
Pick two mountpoints — a base with broadcast station coordinates (RTCM
1005/1006) and a rover — and solve the baseline between them in real time:
double-differenced code + carrier phase, per-epoch integer ambiguity
resolution, FIX/FLOAT status and centimetre-level scatter. Deep-linkable as
?rtk=host:port/BASE|host:port/ROVER. Find it in the
Live RTK baseline section of the workbench
above.
Related Tools
- Stream Inspector — inspect & decode any live stream message-by-message (NTRIP, TCP, USB)
- Broadcast Ephemeris — live satellite health and orbital parameters from the IGS
- RINEX Viewer — analyze recorded RINEX observation files offline
- Positioning Calculator — convert station coordinates between ECEF, geodetic and UTM
- GPS Time Converter — convert GPS time, week number and other GNSS time scales
- Signal Spectrum — interactive PSD chart of all GNSS L-band signals
NTRIP FAQ
- What is NTRIP?
- NTRIP (Networked Transport of RTCM via Internet Protocol) is a protocol for streaming GNSS correction data over the Internet. A caster distributes data from GNSS reference stations to connected clients for RTK and DGNSS positioning.
- What is the difference between NTRIP 1.0 and 2.0?
- NTRIP 1.0 uses ICY-style responses (non-standard HTTP). NTRIP 2.0 uses standard HTTP/1.1 with chunked transfer encoding and the Ntrip-Version header. Most modern casters support both versions.
- What is a sourcetable?
- A sourcetable lists all available data streams (mountpoints) on a caster. Each entry includes the mountpoint name, data format, GNSS systems, location, bitrate, and authentication requirements.
- What is RTCM?
- RTCM is a binary format for GNSS correction data. RTCM 3.x uses MSM (Multiple Signal Messages) to carry observations for all constellations — GPS, GLONASS, Galileo, BeiDou and more.
- What are MSM messages?
- MSM (Multiple Signal Messages) are RTCM 3 message types (1071-1137) that carry full GNSS observations per constellation. MSM4 provides pseudorange and carrier phase; MSM5 adds Doppler and C/N0; MSM7 provides full-resolution observations.
- What is RTK?
- RTK (Real-Time Kinematic) positioning double-differences carrier-phase observations between a base station at a known position and a rover. Satellite and receiver clock errors cancel, and on short baselines atmospheric delays largely cancel too, leaving centimetre-level geometry once the integer carrier ambiguities are resolved.
- What do FIX and FLOAT mean in RTK?
- FLOAT means the carrier-phase ambiguities are still estimated as real numbers — accuracy is decimetre-level and improving as the filter converges. FIX means the ambiguities have been resolved to integers and validated by the ratio test, giving centimetre-level baselines. DGNSS means only code (pseudorange) differences contributed, at metre level.
- What is the RTK ratio test?
- After the LAMBDA integer search, the ratio of the second-best to best candidate’s squared residual norm measures how clearly the best integer set wins. A ratio above the threshold (commonly 3.0) accepts the fix; below it the solution stays FLOAT rather than risk a wrong fix.