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

New to RTKdata.com? Start 30‑day Free Trial or get a plan.

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: 2101

  • Data 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.com

  • Host (IP fallback): 13.56.117.10

  • Port: 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 — automatically applies most widely used regional reference frame (recommended).

    • USA: NAD83(2011) (2010.0); Europe: ETRS89 (ETRF2000) (2010.0); Australia: GDA2020 (2020.00); Canada: NAD83(CSRS) (2010.0); New Zealand: NZGD2000 (2000.00); Turkey: ITRF96 (2005.00); Other regions: WGS84 (G2139, mid‑year)

  • AUTO_WGS84 — WGS84 (G2139), mid‑year epoch

  • AUTO_ITRF2020 — ITRF2020, epoch 2015.0

  • AUTO_ITRF2014 — ITRF2014, current epoch

When to leave it on AUTO: Most workflows targeting local or national grids should use AUTO to avoid frame mismatches. Choose AUTO_WGS84 or AUTO_ITRF2020 only if your application requires a fixed global frame end‑to‑end.

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

  1. Connect to your closest regional hostname (or IP fallback) on port 2101.

  2. Select AUTO as the mountpoint (ALL CAPS).

  3. Confirm the UI shows incoming RTCM / Server OK / Connection Status: connected.

  4. 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

PreviousQuick StartNextCoverage Map

Last updated