TL;DR: An RTK GPS system has five parts: a rover receiver, a GNSS antenna, a correction source (your own base station or a network), a communications link (radio or NTRIP over the internet), and software. Together they turn meter-level GNSS into 1–3 cm positioning in real time. Most teams today skip building a base station and subscribe to an NTRIP correction service, which cuts the system down to a receiver, an antenna, and a data connection.
Key takeaways
- Every RTK system needs a rover receiver, an antenna, a correction source, a communications link, and software.
- The three common system types are single base station, Network RTK (VRS), and a commercial NTRIP correction service that delivers either one over the internet.
- A Fixed RTK solution with a quality correction source delivers 1–3 cm horizontal accuracy.
- Costs range from a few hundred dollars (a module plus a subscription) to tens of thousands (survey-grade rovers with your own base and radios).
- Single-baseline accuracy degrades with distance, roughly 20–35 km from the base. Network RTK keeps accuracy consistent across its coverage area.
What is an RTK GPS system?
An RTK GPS system is the set of hardware, correction data, and software that delivers centimeter-level GNSS positioning in real time. A rover receiver tracks satellites, a reference station or network measures signal errors, and a communications link streams those corrections to the rover so it can resolve its position to within a few centimeters.
New to the technique itself? Start with our pillar guide, what is RTK. This page covers the practical side: what goes into an RTK system, the main system types, how to set one up, and what it costs.
RTK system components
An RTK system has five components, and each one affects the accuracy you get in the field.
| Component | What it does | Key spec to check |
|---|---|---|
| Rover receiver/module | Tracks satellites and applies corrections | Multi-band, multi-constellation, RTCM 3.x input |
| Antenna | Captures GNSS signals | Multi-band, stable phase center, multipath rejection |
| Base station or network | Generates corrections | Station density and distance to your work area |
| Communications link | Delivers corrections to the rover | Latency, range, connectivity (radio vs. NTRIP) |
| Software | Configures, logs, and integrates position output | NMEA output, API access, fix-status monitoring |
1. Rover receiver or module
The rover is the RTK device on your vehicle, drone, robot, or survey pole: a GNSS receiver that tracks satellite signals, takes in correction data, and resolves carrier-phase ambiguities to reach a Fixed RTK solution. It comes as an OEM module you integrate into a product or as a complete survey-grade rover. Look for multi-band tracking (L1/L2/L5) and multi-constellation support (GPS, GLONASS, Galileo, BeiDou), which speed up fixing and improve reliability under partial sky view. For a selection framework, see how to choose the best RTK.
2. Antenna
The antenna often limits accuracy more than the receiver does. A multi-band antenna with a stable phase center and good multipath rejection will outperform a basic patch antenna on the same receiver. Mount it with a clear sky view and a proper ground plane, away from noisy electronics.
3. Base station or correction network
Corrections come from a reference receiver at a precisely surveyed location. It compares what it observes with what it should observe and sends the difference to the rover. That reference can be your own base station or a provider’s network of stations. Our guide to RTK corrections explains how corrections are generated.
4. Communications link
Corrections have to reach the rover with low latency. There are two common links:
- UHF/VHF radio: a direct link from your own base to the rover. It works without internet but needs line of sight and usually reaches less than about 10 km.
- NTRIP: streams corrections over cellular, Wi-Fi, or Ethernet. Range is limited only by network coverage, and it’s the standard way to reach correction services.
Either way, corrections are encoded in the RTCM 3.x format.
5. Software
Software handles configuration (NTRIP credentials, mountpoint, output rates), monitors fix status, and passes position data to your application, usually as NMEA sentences or through an API. For fleets, centralized device provisioning and logging matter as much as the position itself. Point One’s GraphQL API handles both.
Types of RTK systems
RTK systems differ mainly in where corrections come from and how they reach the rover.
| Single base station | Network RTK (VRS) | NTRIP correction service | |
|---|---|---|---|
| Correction source | One base you own and operate | Several stations combined into a virtual reference station near you | A provider’s managed network (single-baseline and/or VRS) |
| Delivery | Usually radio, sometimes your own NTRIP caster | NTRIP | NTRIP |
| Effective range | ~20–35 km from the base | Anywhere in network coverage | Anywhere in the provider’s coverage |
| Setup effort | High: survey, install, and maintain the base | None for the user | None: credentials and a data connection |
| Best for | Remote sites with no cellular or network coverage | Wide-area and mobile operations | Most production deployments |
Single base station
A single-base RTK system pairs your rover with one reference station, often a portable base set up on site and linked by radio. It works anywhere you can deploy a base. The tradeoff is that you carry the cost of surveying, installing, and maintaining it, and accuracy drops with distance. For the full cost breakdown, see whether building your own RTK base station is worth it.
Network RTK
Network RTK uses observations from several surrounding stations to build a virtual reference station (VRS) near the rover. This keeps the effective baseline short across the whole coverage area and adds redundancy if one station goes offline. For how networks work, see our guide to the RTK network. Single-baseline and Network RTK are both observation-based (OSR) approaches, and in practice station density matters more for real-world accuracy than the method, a case we make in why network RTK density matters.
NTRIP correction service
A commercial NTRIP service gives you subscription access to a professionally managed network, with no base station to build. You connect your receiver to the provider’s caster and start receiving corrections right away. Free options such as state DOT CORS networks and community casters exist, but they typically come without uptime commitments or support. For an evaluation framework, see our NTRIP and RTK service provider guide.
The Point One RTK Network works with any RTK-capable receiver and delivers single-baseline and Network RTK from one mountpoint, backed by 3,000+ base stations and 99.9% uptime.
How to set up an RTK system
With an NTRIP service, setting up an RTK system takes minutes once the hardware is mounted.
- Define your requirements. Decide on the accuracy you need, your operating area, real-time vs. post-processed workflows, and whether you’ll have cellular coverage. These determine the system type.
- Choose a receiver and antenna. Pick a multi-band, multi-constellation receiver that accepts RTCM 3.x, and an antenna matched to it.
- Mount the antenna. Give it a clear sky view and a ground plane, away from motors, ESCs, and other RF noise sources. Measure the antenna offset if your application needs it.
- Pick your correction source. Check coverage in your operating area, for example with Point One’s RTK Finder. If you’re running your own base, survey its position precisely.
- Configure the communications link. For NTRIP, enter the caster host, port (usually 2101), mountpoint, and credentials. VRS services also need the rover to send its approximate position as an NMEA GGA message. For radio, match the frequency and protocol on the base and rover.
- Confirm a Fixed solution. Watch the fix status move from Float to Fixed. With good sky view and a quality correction stream, this typically takes seconds.
- Validate and integrate. Check accuracy against a known control point, then route the position output (NMEA or API) into your application, logging, or fleet tools.
For a drone-specific walkthrough, see our drone RTK guide. For surveying workflows, see RTK survey.
How much does an RTK system cost?
RTK system cost depends mostly on receiver grade and whether you build your own base or subscribe to a service.
| Item | Typical range (approximate) |
|---|---|
| Rover hardware (receiver/module + antenna) | ~$200 for an OEM module setup to $20,000+ for a survey-grade rover |
| Own base station (receiver, antenna, mount, survey) | ~$2,000–$20,000+, plus ongoing maintenance |
| UHF radio link | ~$500–$3,000 per pair |
| Commercial NTRIP correction service | ~$50–$200 per device per month |
| Free corrections (state CORS, community casters) | $0, with no SLA or support |
A module-based system on an NTRIP service can come in under $1,000 in hardware plus a monthly subscription. Survey crews running their own base and radios often spend tens of thousands upfront. The base station is where costs are usually underestimated, because surveying, monumenting, monitoring, and replacement add up on top of the hardware. Our build-your-own RTK analysis covers the full three-year cost of ownership. For Point One plans, see RTK pricing.
Choosing the right RTK system
- Choose a single base station if you work at remote sites with no cellular coverage and can survey and maintain a base.
- Choose an NTRIP service with Network RTK if you operate across wide areas, run mobile fleets, or want to avoid infrastructure entirely.
- Add sensor fusion if you work in urban canyons, under canopy, or through tunnels. RTK alone can’t hold position when satellites are blocked. A tightly coupled GNSS/INS system or Point One’s Positioning Engine keeps accuracy through outages.
Accuracy also depends on distance to the reference. See RTK accuracy over distance for the details. RTK systems are used in precision agriculture, construction surveying, drones, robotics, and autonomous vehicles.
Frequently asked questions
What are the components of an RTK GPS system?
An RTK GPS system has five components: a rover receiver or module, a GNSS antenna, a correction source (your own base station or a network), a communications link (radio or NTRIP), and software for configuration and data output.
Do I need my own base station for RTK?
No. A commercial NTRIP correction service gives you access to a managed network of base stations over the internet, so you only need an RTK-capable receiver, an antenna, and a data connection. Your own base mainly makes sense at remote sites without cellular coverage.
How accurate is an RTK system?
With a Fixed RTK solution, good sky view, and a nearby or network-generated reference, an RTK system typically delivers 1–3 cm horizontal accuracy. Accuracy degrades with distance from a single base station, while Network RTK keeps it consistent across the coverage area.
What is the difference between single-base RTK and Network RTK?
Single-base RTK uses corrections from one physical reference station, and accuracy drops with distance, roughly beyond 20–35 km. Network RTK combines several stations into a virtual reference station near the rover, which keeps accuracy consistent and adds redundancy if one station drops out.
How much does an RTK GPS system cost?
A module-based system on a correction service can cost under $1,000 in hardware plus about $50–$200 per device per month. Survey-grade rovers with your own base station and radios can cost tens of thousands of dollars upfront, plus ongoing maintenance.
How do I connect an RTK receiver to an NTRIP service?
Enter the provider’s caster host, port (usually 2101), mountpoint, and your credentials in the receiver’s configuration. If the service uses VRS, enable NMEA GGA output so the rover reports its approximate position. Then confirm the fix status reaches Fixed.
Get started with RTK corrections
The fastest way to a working RTK system is a quality receiver, a well-mounted antenna, and a correction service you don’t have to maintain. Start your free trial of the Point One RTK Network, or contact our team to talk through your deployment.
