Minimum Mobile Internet Quality Required for Stable RTK Operation

Categories
Table of contents
  1. Minimum Internet Speed for RTK to Work
  2. What Ping Is Critical for an RTK Navigation System
  3. Does RTK Work Over 3G, Edge, and 4G
  4. What Happens When the Signal Drops in the Field
  5. How to Check Connection Quality Before Heading Out
  6. Do You Need a Dedicated Router, or Is a Phone Enough
  7. The Bottom Line

For stable RTK navigation, a mobile connection with a speed of 10–15 Kbps and a latency (ping) of up to 2 seconds is sufficient. Even a steady Edge or 3G signal covers this requirement completely. What matters here is not megabits per second, but a stable connection without prolonged dropouts.

Minimum Internet Speed for RTK to Work

RTK corrections are delivered via the NTRIP protocol in RTCM format. This is an extremely compact data stream — according to the NTRIP specification published by the German Federal Agency for Cartography and Geodesy (BKG), it requires just 0.2 to 10 Kbps. In real agricultural conditions, the average download rate for corrections is around 12 Kbps.

For reference: a regular mobile voice call requires 8–13 Kbps. In other words, an RTK navigator consumes roughly the same bandwidth as a phone conversation. Parallel driving systems based on RTK, used in precision agriculture, do not need broadband internet — a stable channel is all that's required.

Over a full working day (10 hours in the field), an RTK session uses an estimated 50–70 MB of data — less than a single high-quality photograph.

What Ping Is Critical for an RTK Navigation System

Download speed is only half the picture. Latency — the time between requesting corrections and actually receiving them — is far more important. RTK is a real-time system, and if data arrives late, accuracy suffers.

Research by Yan et al. (2009) demonstrated that latency exceeding 2 seconds begins to measurably degrade positioning accuracy. The optimal figure is under 1 second, which is what leading RTK network providers recommend. If the correction age stays within 0.4–1.0 s, the system is operating correctly.

Latency (ping) Correction age RTK status
under 500 ms under 1 s Excellent — stable Fix
500 ms – 2 s 1–2 s Acceptable — accuracy within spec
2–4 s 2–4 s Degraded — accuracy declining
over 4 s / dropout over 4 s Critical — Fix at risk

Does RTK Work Over 3G, Edge, and 4G

The short answer is yes — even over GPRS. Tests carried out under the EUREF project (European Reference Frame network) showed that transmitting RTCM corrections via mobile networks of any generation does not lead to noticeable RTK accuracy degradation. GPRS produces latency under 2 seconds, which falls within the acceptable range.

Standard Typical speed Typical ping RTK navigation
GPRS (2G) 20–50 Kbps 300–1000 ms Marginally usable
Edge (2.5G) 100–200 Kbps 150–500 ms Sufficient
3G (UMTS/HSPA) 1–10 Mbps 50–150 ms Good
4G LTE 10–100 Mbps 10–50 ms Excellent

The issue with GPRS and Edge is not speed but instability. A signal that keeps dropping and reconnecting is far worse than a slow but consistent stream. On fields with poor coverage, test connectivity in advance rather than discovering the problem mid-operation.

What Happens When the Signal Drops in the Field

This question concerns practically everyone starting out with RTK. The good news is that brief dropouts are not a disaster. Most modern RTK receivers support a coasting mode — maintaining a fixed solution even without receiving fresh corrections.

The typical coasting duration is 3–4 minutes. If the connection is not restored within that window, accuracy drops sharply: the system falls from centimetre-level to decimetre-level, and then Fix is lost entirely. Once connectivity is restored, re-initialisation is needed, which takes anywhere from a few seconds to about a minute.

Dropouts of 10–20 seconds are not critical. Dropouts lasting 5 or more minutes during active fieldwork are a real problem and will show up in the quality of the pass.

How to Check Connection Quality Before Heading Out

The check takes 2–3 minutes and saves you from unpleasant surprises in the middle of a field. Here is a practical sequence:

  • Open any speedtest service (such as fast.com or speedtest.net) right from the field or the area where you plan to work.
  • Focus on ping — it should be under 2000 ms. Download speed is largely irrelevant as long as it is above 20 Kbps.
  • Check stability: if a page loads normally without freezing, the connection is adequate for RTK.
  • If coverage is unstable, try fitting an external antenna or using SIM cards from different carriers — coverage can vary significantly across the same field depending on the operator.

Also watch the correction age indicator in your navigator's software. If it consistently stays below 1–2 seconds, everything is fine. If it spikes above 4–5 seconds, troubleshoot the connection quality before looking for a fault in the hardware itself.

Do You Need a Dedicated Router, or Is a Phone Enough

For most field tasks, a smartphone in hotspot mode is sufficient. If you plan to operate in areas with weak coverage, a mobile LTE router with an external antenna is worth considering — it holds the connection more reliably than a phone and will not die after an hour of heavy use.

On large farms with known dead zones, some operations use Starlink — low-Earth-orbit satellite internet. It delivers latency of 20–60 ms and sustains RTK Fix at a level comparable to terrestrial networks.

The Bottom Line

RTK navigation is one of the least bandwidth-hungry technologies that rely on an online connection. Very little data is needed, but the connection must be stable and low-latency. A solid 3G signal in the field is more than enough for centimetre-level accuracy throughout the entire working day.

( 6 )
Comments
No reviews yet
Write your comment
Name*
Email
Enter your comment*