RTK2Go Alternatives: When Free NTRIP Isn’t Enough for Professional Work

What Is RTK2Go?

RTK2Go is a community NTRIP caster run by the makers of the SNIP caster software. Anyone with a GNSS base station can push an RTCM stream to it, and anyone with an NTRIP client can connect to a listed mountpoint without paying. The operator describes it as a no-cost service for publishing your base station data and exchanging it with others. Client access is free "and will remain so" (SNIP, operator page, retrieved 21 September 2026). New to casters and mountpoints? Start with our NTRIP explainer.

The caster itself is professional software, but the streams on it are not the caster's. Each belongs to whoever registered the mountpoint. That person decides where the base sits, what coordinates it broadcasts and whether it stays online. A stream on a community caster is a contribution, not a service.

RTK2Go's Reliability Limits

The terms of use on the connection page are explicit. By sending a stream you consent to others using it freely. The caster operator is held harmless for any faults or loss (How to Connect page, retrieved 21 September 2026). There is no uptime figure, no SLA and no restoration commitment for any stream. That is not a hidden flaw. It is the deal.

The caster publishes a support address, and registration asks for a working email so the software can send the operator an error report when a stream fails. Neither obliges that operator to fix anything before your crew is in the field with a receiver stuck in float.

Caster availability and station availability are different things. The caster can be up while the one mountpoint within range of your site has been silent since Tuesday. Plan for that stream to vanish without notice; nothing prevents it. Volunteer-run does not mean badly run. It means unaccountable to you.

Datum Accuracy on Crowdsourced Base Stations

An RTK rover computes where it is relative to the base, then adds the base coordinates carried in the RTCM stream. If those coordinates are a metre off, every point you collect is a metre off, and the receiver still reports a fixed solution with centimetre precision. A crowdsourced network guarantees precision at best, never absolute accuracy.

On a community caster nobody verifies the base position or the frame it was entered in. The connection guide says frame adjustments such as NAD to WGS are handled on request; the frame is whatever the contributor set. That does not matter for repeat passes over one field within a session. It matters when a deliverable must tie to published control. In the United States that means NAD83(2011) at epoch 2010.00. NGS uses that frame for CORS coordinates alongside ITRF2014 (NGS CORS FAQ, retrieved 21 September 2026).

RTKdata's AUTO mountpoint delivers corrections in the regional datum for your location, NAD83(2011) in the US, ETRS89 in Europe, GDA2020 in Australia, plus ITRF2020 and WGS84 options. Our documentation on coordinate systems and datums lists every region. It notes that a steady offset of half a metre or more against local control usually means a datum mismatch. That gap widens every year with plate motion (retrieved 21 September 2026), as our guide to WGS84, NAD83 and ITRF explains. Before trusting any stream, free or paid, occupy one known control point and compare.

GEODNET, CORS Networks and Other NTRIP Options

GEODNET is a decentralized network of independently operated base stations. It reports more than 20,000 active stations, streams RTCM 3.2 over NTRIP and delivers corrections in WGS84, ITRF and NAD83 plus regional datums (network page, retrieved 21 September 2026). Its stations are crowdsourced, but it is not a free service: standard access is a subscription at $40 per month or $400 per year (official store, retrieved 21 September 2026).

CORS, the Continuously Operating Reference Station system, is the public option. NGS itself does not stream corrections. Real-time access comes from contributors, mostly state departments of transportation, which the NGS FAQ says may provide RTK streaming with or without subscription fees (retrieved 21 September 2026). Minnesota's MnCORS runs receivers at more than 140 known positions, describes its output as survey grade and names an administrator contact (MnDOT, retrieved 21 September 2026). Where a state CORS network covers your project it is a professional choice; its limits are the state line and, on some networks, account eligibility or fees.

Other free casters, usually private ones shared by a company, university or farm cooperative, get the same three questions. Who owns the base station, what frame does it broadcast, and what happens when it goes dark?

Free NTRIP vs. Paid RTK: Which Fits Your Project

The rule is not about price. It is whether the stream's provenance, reference frame, availability arrangement and your own check against control meet the specification.

Here is how the four options covered above compare on those criteria, as documented at the time of writing:

A free NTRIP service is a reasonable choice when the work is relative. That covers pass-to-pass guidance or repeat mapping of one site within a session. It also fits when nobody outside your team relies on the coordinates. The same goes when a lost fix costs an afternoon rather than a contract, or when you are testing hardware.

A paid or formally supported service is the defensible choice when any of these is true:

• The deliverable carries legal, liability or client stakes: boundary work, as-builts, stakeout, anything a third party signs off.
• The coordinates must match a published reference frame, so the network has to state which frame it delivers.
• A dropped stream means a revisit, a rescheduled crew or a missed weather window, so availability has a price you can calculate.
• The job moves across regions, and one account has to work in all of them.

The word free is not on that list. A state CORS network with a documented frame and an administrator you can email may satisfy every line; an unverified volunteer stream satisfies none, whatever it costs.

RTK Correction Pricing

RTKdata is a paid RTK correction service. Its RTK correction pricing is $40 per month for one device in concurrent use, $400 per year, or $1,920 once for five years (retrieved 21 September 2026). The subscription network above lists the same $40 and $400; the community caster costs nothing.

The $40 does not buy corrections; a volunteer stream carries the same RTCM messages. It buys the layer above the stations. One account draws on several networks plus RTKdata's own hosted bases, with sub-second failover across redundant casters. The terms of service commit to 99.99% online time for network access. The network documentation states 99.99% uptime at the NTRIP endpoints. Add a support desk and a stated reference frame per region. Coverage runs to 20,000+ reference stations across 140+ countries, checkable on our network coverage map (all retrieved 21 September 2026). The terms are equally clear that continuous availability everywhere, or a fixed solution under every sky, is not promised.

Run your own arithmetic for one lost half day. Add crew hours, travel both ways and whatever a delayed client costs you. Then set the total against $40 a month or $400 a year. For a crew billing survey-grade deliverables, one avoided revisit usually covers the annual fee, before the datum risk is priced at all.

RTK Baseline Distance Limits

RTK assumes the atmosphere over the rover matches the atmosphere over the base, and that assumption weakens with distance. NGS's single-base real-time guidelines put the limit at baselines of 20 km or less (retrieved 21 September 2026). RTKdata's accuracy guidance says work within 15 km of a base station. Our article on how distance affects NTRIP RTK accuracy shows how the error grows. Beyond that range the receiver converges more slowly, and the fix vs. float indicator flickers.

Coverage density is a number you can check. A caster whose nearest stream is 35 km from your site is not covering your site. Some networks bridge the distance with a virtual reference station computed near the rover. RTKdata's AUTO mountpoint instead picks the nearest physical base station from your receiver's GGA position, in the regional datum. Either way, ask: how far is the nearest usable base, and what happens to my baseline distance if it drops? Check your site on the coverage map.

FAQ