The Front Page for

RTK2go is a community NTRIP Caster to allow you to publish your GNSS correction streams for others to use with their NTRIP Clients.  It is built using the Pro edition of the SNIP Caster.  It is one part of the overall simple NTRIP project created by SubCarrier Systems Corp. (SCSC).

It accepts data from other SNIP nodes, the Simple NTRIP Caster, in the PUSH-Out mode, as well as from other NTRIP Server software.  It is not a web site.  If these terms are unfamiliar to you, just click on these links for further explanations.

But if these terms are familiar to you, you probably want to know how to log on.

This is a simple “one page web site” as all the interesting things take place using the normal NTRIP protocol layers hosted on the same machine.


How to Connect:

When connecting to RTK2go as an NTRIP Client no log-on is required.  We run this caster in an open mode.  Simply point your NTRIP client to:   (port 2101).   [Hint: You can also point any common browser this this pages as well, but the most recent release of Chrome now gets picky when it sees the the textual Caster Table returned rather than a web page and refuses to show it]

When connecting to this site as an NTRIP Server (to send data to RTK2go) an account password is needed. Point your server to:   (port 2101).  This password will vary over time to prevent abuse, but at this time the password is BETATEST  (all caps).  Any well formed NTCIP connections are allowed.

Terms of Use: By sending your data to this Caster you affirm that a) you have the right to do so, and b) you consent to allow others to freely use your data, and c) the caster owner / operator shall be held harmless for any faults or loss – real or perceived.   The caster owner / operator (SCSC) reserves the right to remove or block any party for abuse.

The number or the diversity of streams which your (or you end users) NTRIP clients will see at any given time depends on who else is logged on any any given time and providing stream data.  The image below was taken on April 20th and shows a few European “emlid” or “Reach” users sending RTCM 3.x style data through the RTK2go Caster.  FYI, this is an image from SNIP‘s basic map display mode.


At any given time you will likely see RTCM correction streams from all over the world.  This is shared resource, but just inform your users what mountPt is yours.  If your personal chosen mount point name is suddenly labeled xxx_02 it means you (or another party) have sent RTK2go the same name for a mount Point more that once.  SNIP will not  mind but it will confuse your end users who will be seeking for xxx.  Unless you are using very common terms like “test” for you mountPt you will probably never experience this. And please keep in mind that mount point names are case sensitive.  This article can be helpful.

Most published streams are in the RTCM3 format, but there is no restriction or limit on this.  The uBlox proprietary format is also popular for 6T and 8M devices (uBlox is a low cost L1 only device).  Often people use the RTKLIB‘s STRSVR (Stream Server) tool (written by Tomoji Tokasu) to translate these device feeds into RTCM 3.x before pushing them to RTK2go, or to their own copy of SNIP.

If you want to determine a rover device’s position with either SNIP or with a 3rd party app by reading the data you publish, then RTCM3 is the message set you will need to support.  Over the last few years or so, many inexpensive devices (such as the uBlox 8MT chip) can now also output in the RTCM3 format directly.   If your Android phone has the “Nougat” operating release or better, it too can send RTCM3 data to our Casters using some free 3rd party apps.

Right now we are running this Caster in SNIP‘s “non parsed” mode so that whatever you send to it in PUSH-In mode is available to others.  You (that is, your NTRIP Server software) needs to fill out the Caster Table entry for your data in the normal way.  Most network operators prefer to run their own copy of SNIP in with the default parsed mode enabled, so that any inbound RTCM3 streams will have the caster table entries automatically filled in and/or corrected for them.  And incidentally, most network operators do not you want you to send them your data stream unannounced. [SNIP owner/operators: You can use the List Recent IPs… button (on the Clients Tab next to the List Current Users… button) to see a list of the IP addresses that have tried to connect to you.  The Ban.. button allows managing the list of IPs which have been banned for a periods of time for abuse.]


NTRIP Clients that get no Data:

There is a section of the SNIP knowledge base on managing user accounts has some articles on debugging NTRIP Client connections with commonly occurring error that may be of value to you in resolving this.   If you are having issues, please send us an email [support [at]] and we will create a support ticket.

NTRIP Caster networks are independent of each other.  And while the world-wide community shares a lot of common data, it is also incorrect to presume that any Caster has immediate access to the data streams from another Caster.  Said another way; In NTRIP there is no concept of an inter library loan system that will locate a mountPt on another caster for you.

If your rover’s (NTRIP Client) repeated connection attempts to a Caster result in just getting the Caster Table returned to you and a disconnect, either that Caster does not have the data you seek or you do not have a user account with that Caster operator.  It is considered bad form to reconnect to a Caster every second for hours on end if your connection attempt is being rejected.  Most Casters are not operated in an open mode as this one is.


Real Time Status:

The SNIP node on this site and the RTK2go web site (this page) are hosted on the same machine(s).  To determine if SNIP is up and operational, simply request the Caster table ( ).  If you get a Caster table returned, then that copy of SNIP is on line.  This method can be used for most NTRIP Casters in the world.

Please Note that the latest release of Chrome will now claim that any returned text page is a “invalid response” and not show the Caster table.  [Aside: We may wrap the table in html whenever a browser asks for it in the next release of SNIP which will easily overcome this, but we want to pass that idea around at the next RTCM SC-104 meeting (where the NTRIP protocol is maintained) before doing so.]

How to get your IP banned:

The SNIP node on this site employs the SNIP Enterprise IP tracking logic to detect and block addresses that continually abuse the machine in an attempt to connects or to attack it.  A count is kept of the number of “bad” or failed connections seen for any IP address.  This value is reset on any successful connection or after a period of non use.  If the value grow too large (thousands of failed connections) the IP is banned for a period of time (~15 minutes).  These are all threshold values which the operator can set.  An aggressive NTRIP Client can get itself banned by attempting to connect once per second for a hour or two.  A more normal NTRIP Client might see this after 2 days of trying to connect without success.  In either event, the client will get an html 500 message back until the banned period has passed at which time its connection will again be processed.   The most common cause of this event is benign; its simply an NTRIP Client trying to connect to a stream that does not exist.   If this happens to your device, it indicates you have some fundamental issues with your connection you need to work out.  SNIP operators are advised to set these levels much lower on their own machines.


How it works:

In SNIP and NTRIP terminology:  You send your data (from a remote copy of SNIP using a PUSH-Out stream, or from any other valid NTRIP Server you wish to use) to the SNIP node (which is an NTRIP Caster).   That SNIP node (this machine) accepts your data (creating a new PUSH-In stream) and then publishes a new table entry in its Caster Table, making your data stream available to any NTRIP Client user who cares to connect.    If you poke about on the web you will find many images like this one used to describe the components of an NTRIP system.



Prefer to have a Caster of your own on your own machine? – that is just what SNIP was developed for.  And for small network user, it is free.

Prefer to have a Caster of your own but do not have a static IP or your host PC is behind a firewall – then this RTK2go site provides a community solution for that.

Want to run a network of RTK connections which you can then sell to others? – that is also what SNIP was developed for.  Unlike many other providers of NTRIP Caster technology; we don’t want to resell your data and we do not have any monthly usage fees.  The Basic and Pro models of SNIP support this use case with a very attractive ROI for business users.  See our extensive knowledge base for details.

Need us to provide you with dedicated a SNIP Caster with a special requirements, our Enterprise Edition was developed for these sorts of unique needs.


Important Feature: Reservations

Prefer to have your mountPt string and settings reserved?  The reservation feature of SNIP allows this.  Drop at note to our support team,  support [at] and we can set that up for you.   Want you mountPt to be private so that other do not see it, let us know that as well.  We need to know the name you want for you stream, and if is to be parsed.  A short note about how you are using the data stream is useful to us, but is not required.  The name for your home town is also helpful to add to the Caster Table entry.

There is no cost for this.  We are now running this Caster to default any PUSH-In new connection as “unparsed” in order to support our CMR user community.  But a reservation with parsing enabled is also the best way to send SNIP RTCM 3 messages and have it parse over them and setup the Caster Table Entry automatically for you.

NOTE: A note to “emlid” or “Reach” users:  Please consider getting a reservation setup with us.  If you are sending RTCM data to this node, and if creating the Caster Table entry is too complex, then let SNIP automatically do it for us.  As per the above, drop us a short email and get a reservation.


None.  This service is free to all users, and yes you may use it for commercial purposes subject to the Terms of Use above.  If you require dedicated hosting and monitoring services, please contact us below.  We reserve the right the changes this policy if required, but at the present time do not foreseen any need.


How to Begin:

  1. Forward the local RTK data stream of interest to using SNIPRTKLIB,  or any  NTRIP Sever or relay tool (many GNSS devices include a built-in NTRIP Server function).  If your GNSS device does not provide this ability, use a Lite copy of SNIP with the correct data stream type to forward it for you.
  2. Connect as many rover devices to as you need from the internet using your favorite NTRIP Client tools
  3. Enjoy RTK and centimeter level precision

If you are new to RTK corrections being transmitted by NTRIP over the internet, you may want to learn about our flagship product SNIP, a robust but low cost tool for creating your own NTRIP Caster with a network of RTK corrections. If you need an NTRIP Caster, you will find SNIP to be the best solution available.

Also, the open caster for community use is maintained at (at port 2101) and we do not allow new data streams to be added to it. Please use for that.



Are always welcome, please send them to support [at] We use your comment to help us make SNIP the best caster tool in the world.

RTK Logo 04

SNIP® and RTK2go® are registered trademarks of SubCarrier Systems Corp. (SCSC).