RTK network map & directory

A public map and list of correction networks worldwide, built from public NTRIP sourcetables. It shows what exists, where it is and — where the community measured it — how healthy it is.

Two map layers

The toggle above the map switches between two views that must not be confused:

• Mapped — public caster data from their sourcetables. It says what exists: caster addresses, mountpoints, advertised constellations and RTCM versions. It is not a measurement — a catalogue, not a health state.
• Live-checked — places where the Fixcast community actually measured quality by connecting to the stream. This is real stream health, not just an advert.

What the counts mean

The summary stats separate two different things:

• streams = individual mountpoints (one caster usually has many);
• ≈ stations = an estimate of physical reference stations after removing overlap — the same station is often shared by several networks, so the stream count overstates how many stations there really are.

Station markers & privacy

Small dots are approximate station positions (~1 km) derived from public sourcetables. For commercial/pro networks we show the mountpoint code; for community relays the station name is withheld — this protects the privacy of people running a station at home. If one station is shared by several networks, the marker says so.

Network types

• commercial — paid survey networks;
• state / geodetic — national mapping services;
• academic — university and research networks;
• community relay (aggregated) — open casters such as rtk2go, where mountpoints belong to different people; shown aggregated and without station names.

Station badges

In a network's detail, stations carry GNSS badges (constellations: GPS, Galileo, GLONASS, BeiDou…) and RTCM badges (message versions). These come from the advertised sourcetable — declared capabilities, not a measured state. The real state shows only once you connect to the stream (the live-checked layer or the mobile app).

Receiver compatibility

The Compatibility page compares a chosen receiver against the streams in the directory and flags where a problem might occur before you connect. It checks four things:

• MSM vs. legacy — whether the receiver handles newer MSM messages or only old legacy ones;
• SSR vs. OSR — whether the stream sends state-space (SSR) corrections the receiver can't use;
• VRS / network mounts — a network mount requires the receiver to send its position (GGA);
• constellations — whether the receiver tracks the satellite systems the stream carries.

Verdicts are OK / partial / incompatible / unknown and are indicative — based on datasheets. A definite verdict comes only from decoding the real stream (the mobile app).

Adding a caster to the map

Run your own caster and it isn't on the map? Add it with the “Add your caster” button — you enter the sourcetable address and a contact e-mail, a verification link arrives and once confirmed the caster appears in the directory. This is only a public-directory listing; managing reports, the dashboard and remote support belong to an operator account.