Network
Use RTKdata.com’s regional hostnames or IP fallbacks with Port 2101 and one of four valid mountpoints (AUTO, AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014). This page is the single source of truth for all
Network & Mountpoints - RTKdata.com Hosts, IPs, Port 2101 & AUTO Settings
Configure your rover, receiver, or drone to stream RTK corrections from RTKdata.com in minutes. This page consolidates connection settings, regional endpoints, valid mountpoints, and vertical reference so crews get to RTK: FIX fast.
Why RTKdata.com (at a glance)
20,000+ reference stations globally (multi‑constellation network; nearest base is auto‑selected via your GGA).
99.99% service availability at NTRIP endpoints (12‑month rolling, internal monitoring).
Fast FIX in open sky: typically 5–20 s (may be longer in obstructed areas).
Low latency: median ≤ 1.2 s rover‑to‑caster roundtrip (typical cellular links).
Simple mountpoints (ALL CAPS):
AUTO,AUTO_WGS84,AUTO_ITRF2020,AUTO_ITRF2014.
Notes on figures: Station count reflects the federated footprint we aggregate across partner networks; availability refers to our NTRIP caster endpoints (excludes local ISP/cellular outages on the rover). Performance depends on sky view, RF environment, and cellular quality.
Connection settings (all devices)
Protocol: NTRIP or NTRIPV2
RTK Login: Go to RTKdata.com dashboard. In the RTK Credentials section, copy your RTK username and password (note: these are different from your website login details).
Port:
2101Data stream: Select a mountpoint
Your device UI may label fields as Caster address / Server / Host / IP and Mount Point / Stream / Source Table.
Regional endpoints - use hostname first, IP if required
Use the nearest regional RTKdata.com server hostname for your location. If your device requires a numeric host or your network blocks DNS, use the numeric IP fallback.
Host (domain):
rtk.rtkdata.comHost (IP fallback):
13.56.117.10Port:
2101
Host (domain):
eu.rtkdata.comHost (IP fallback):
3.73.41.96Port:
2101
Host (domain):
aus.rtkdata.comHost (IP fallback):
54.206.56.130Port:
2101
Make sure any firewall or APN allows outbound TCP :2101 to the endpoint you select.
Valid mountpoints (ALL CAPS)
Only these four mountpoints are valid. Type them exactly as shown (ALL CAPS). Using local coordinate system names (e.g., “EPSG:####”, “NAD83PA11”) will not stream corrections.
AUTO
Regional Geodetic Coordinate System (RGCS) – automatically adjusts to the local datum.
AUTO_ITRF2020
ITRF2020 at the current epoch.
AUTO_ITRF2014
ITRF2014 at the current epoch.
AUTO_WGS84
WGS84 (G2139) at the mid-year epoch (e.g. 2025.5), following NGS recommendations.
Geodetic Coordinate System Names (Regional Systems for AUTO)
1
NAD83(2011)
2010.0
USA & North America
2
NAD83(PA11)
2010.0
USA – Hawaii
3
NAD83(MA11)
2010.0
Guam (GUM)
4
NAD83(CSRS)v7
2010.0
Canada (CAN)
5
ETRS89(ETRF2010) (2010.0)
2010.0
Europe
6
GDA2020 (2020.0)
2020.0
Australia (AUS)
7
NZGD2000 (2000.0)
2000.0
New Zealand (NZL)
8
TUREF(2005.0)=ITRF96(2005.0)
2005.0
Turkey (TUR)
9
ITRF2008(2005.0)=ITRF2008(2005.0)
2005.0
India (IND)
11
ITRF2008(2011.811)
2011.811
Egypt (EGY)
12
NGD2012(2012.0)=ITRF2008(2012.0)
2012.0
Nigeria (NGA)
13
PGD2020 = ITRF2014(2020.044)
2020.044
Philippines (PHL)
14
ITRF2014 (2010)
2010.0
Mexico (MEX)
15
ITRF2014 current epoch
aktuell
Kenya (KEN)
16
CGCS2000(2000.0)=ITRF97(2000.0)
2000.0
China (CHN)
17
JGD2011(2011.3945)=ITRF2008(2011.3945)
2011.3945
Japan (JPN)
18
IGRS2013(2012.0)=ITRF2008(2012.0)
2012.0
Indonesia (IDN)
19
ITRF1991(1994.0)
1994.0
South Africa (ZAF)
20
WGS84(G730)(1994.0)
1994.0
Sri Lanka (LKA)
21
ITRF2020(2025.0)
2025.0
Taiwan (TWN)
22
ITRF2014 (2010)
2010.0
Thailand (THA)
23
KGD2002(2002.0)=ITRF2000(2002.0)
2002.0
South Korea (KOR)
24
MGRF2020(2020.0)=ITRF2020(2020.0)
2020.0
Malaysia (MYS)
25
MTRF2000(2004.0)=ITRF2000(2004.0)
2004.0
UAE (ARE)
26
SIRGAS2000(2000.4)=ITRF2000(2000.4)
2000.4
South America
27
GGD = ITRF2008(2011.353)
2011.353
Georgia (GEO)
28
WGS84(G2139)(20xx.5)
20xx.5
Other regions (for AUTO_WGS84)
Vertical reference (heights)
RTKdata.com broadcasts positions in the selected geodetic frame; heights are ellipsoidal by design. If you need orthometric (mean sea level) elevations, enable a geoid on your rover/controller (if supported) or apply a geoid in your GIS/photogrammetry workflow during processing/export.
Quick test & verification
Connect to your closest regional hostname (or IP fallback) on port 2101.
Select
AUTOas the mountpoint (ALL CAPS).Confirm the UI shows incoming RTCM / Server OK / Connection Status: connected.
Move outdoors (open sky) and wait for RTK: FIX (you may see Float first).
Common mistakes to avoid
Typing the mountpoint in lowercase or entering a local CRS name as a mountpoint
Using the wrong region (choose the closest regional server)
Blocking TCP :2101 on corporate networks
Expecting orthometric heights without applying a geoid
Last updated