What Is NTRIP? A Practical Guide to RTK Corrections Over the Internet

NTRIP is one of the most important terms to understand when working with RTK GNSS receivers. It is the method many surveyors, construction professionals, GIS users and machine-control operators use to receive RTK correction data through the internet instead of through a local radio link.

In simple terms, NTRIP helps your GNSS rover connect to a correction service so it can calculate a much more accurate position in real time. Without correction data, a GNSS receiver may only provide metre-level accuracy. With the right RTK corrections, a survey-grade receiver can usually work at centimetre-level accuracy, depending on equipment, satellite visibility, correction quality, environment and workflow.

Quick answer: what is NTRIP?

NTRIP stands for Networked Transport of RTCM via Internet Protocol. It is a communication protocol used to stream GNSS correction data over the internet. In RTK surveying, NTRIP allows a GNSS rover to receive correction data from a base station, CORS network or RTK correction service using a mobile data connection.

NTRIP is not the correction data itself. It is the delivery method. The correction data is commonly sent in RTCM format, while NTRIP is the internet-based system that transports that data from a correction source to your rover, controller or software.

A complete NTRIP workflow normally includes a correction source, an NTRIP server, an NTRIP caster and an NTRIP client. The NTRIP server sends correction data to the caster. The caster distributes the available correction streams. The client connects from the field and receives the selected stream for the GNSS rover.

Why does NTRIP matter for RTK GNSS work?

RTK GNSS positioning depends on correction data. A rover in the field receives satellite signals, but those signals are affected by atmospheric delays, satellite orbit errors, clock errors, multipath and local site conditions. RTK corrections help the rover reduce these errors by comparing its measurements with data from a known reference station.

Traditionally, RTK corrections were often sent from a local base station to a rover using UHF radio. That method is still useful, especially on remote sites. NTRIP provides another option: instead of setting up your own base station and radio link, the rover receives correction data over the internet from an RTK network or correction service.

This is why NTRIP is widely used in modern surveying, construction layout, GIS mapping, drone ground control work and machine-control workflows. It can reduce equipment setup time, avoid radio range problems and make RTK positioning more practical across larger working areas.

How does NTRIP work?

An NTRIP setup has four main parts: the correction source, the NTRIP server, the NTRIP caster and the NTRIP client. These names can sound technical, but the field workflow is straightforward when each part is separated.

Part	What it does	Field example
Correction source	Generates GNSS correction data from a known reference position.	A permanent CORS station, a network RTK system or your own GNSS base station.
NTRIP server	Sends correction data from the correction source to the NTRIP caster.	A GNSS base receiver, reference station computer or software service that uploads RTCM correction data to the caster.
NTRIP caster	Acts as the internet distribution point that receives correction streams from NTRIP servers and makes them available to users.	The online correction service platform that lists available mountpoints.
NTRIP client	Connects to the caster, selects a mountpoint and receives the correction stream for the rover.	Your data collector software, GNSS receiver, tablet app or machine-control modem.

The easiest way to understand the system is to think of the NTRIP server as the uploader, the NTRIP caster as the distributor and the NTRIP client as the receiver. The NTRIP server sends correction data into the system. The caster manages and shares the available correction streams. The client connects from the field and receives the stream needed for RTK positioning.

The full correction chain can be shown like this:

Correction source → NTRIP server → NTRIP caster → NTRIP client → GNSS rover

In the field, the process usually looks like this:

1. The correction source, such as a base station or CORS station, tracks GNSS satellite signals from a known position.
2. The NTRIP server sends the correction data from that source to the NTRIP caster over the internet.
3. The NTRIP caster hosts the correction stream and makes it available as a mountpoint.
4. The GNSS rover, controller or modem connects to the internet using a SIM card, hotspot, WiFi or built-in 4G/5G modem.
5. The NTRIP client logs in to the caster using a server address, port, username and password.
6. The user selects the correct mountpoint, which is the correction stream to use.
7. The correction data is received by the rover in real time.
8. The rover uses the corrections to calculate an RTK position, usually shown as fixed, float or single in the field software.

What is an NTRIP server?

An NTRIP server sends GNSS correction data from a correction source to an NTRIP caster. In many professional workflows, the correction source is a base station, CORS station or reference receiver. The NTRIP server takes the RTCM correction messages from that source and uploads them to the caster over the internet.

This is different from the NTRIP client used by the rover. The server is normally on the correction-provider side or base-station side of the workflow. The client is normally on the rover side of the workflow.

For example, if a survey company sets up a GNSS base station on a known control point and wants to make that correction stream available over the internet, the base receiver or connected software may act as the NTRIP server. It sends the correction stream to a caster. The rover crew then connects to that caster as an NTRIP client and receives the stream in the field.

What is an NTRIP caster?

An NTRIP caster is the internet distribution point in the NTRIP system. It receives correction streams from one or more NTRIP servers and makes those streams available to NTRIP clients.

In practical fieldwork, the caster is the server address that you enter into your GNSS receiver, data collector or field software. When you log in, the caster can provide a list of available correction streams, called mountpoints.

The caster does not normally create the GNSS correction data itself. Its main job is to manage, organize and distribute the available streams to authorized users.

What is an NTRIP client?

An NTRIP client is the device or software that connects to the NTRIP caster and receives correction data. In the field, the NTRIP client may be built into the GNSS receiver, data collector, surveying software, tablet app, modem or machine-control system.

When a surveyor enters the caster address, port, username, password and mountpoint in the field software, they are normally configuring the NTRIP client. The client connects to the caster, requests the selected correction stream and passes that correction data to the rover for RTK positioning.

What is a mountpoint in NTRIP?

A mountpoint is the name of a correction stream on an NTRIP caster. When you connect to an NTRIP service, you may see several mountpoints. Each mountpoint can represent a different correction type, reference station, network solution, constellation support or data format.

For example, a correction service may offer separate mountpoints for a single reference station, a VRS network solution or different RTCM message formats. The correct mountpoint depends on your GNSS receiver, software, location and required workflow.

Choosing the wrong mountpoint can lead to slow fixing, no RTK fix, incorrect coordinates or poor performance. For professional surveying, it is important to check that the mountpoint supports your receiver, satellite constellations, correction format and coordinate reference system.

NTRIP, RTCM and RTK: what is the difference?

NTRIP, RTCM and RTK are closely related, but they do not mean the same thing.

Term	Meaning	Simple explanation
RTK	Real-Time Kinematic positioning	The positioning method that uses correction data to calculate accurate GNSS coordinates in real time.
RTCM	Radio Technical Commission for Maritime Services correction format	A common format used to package GNSS correction messages.
NTRIP	Networked Transport of RTCM via Internet Protocol	The internet-based method used to deliver correction data to a rover.

A simple way to understand it is this: RTK is the positioning method, RTCM is commonly the correction message format, and NTRIP is the internet delivery system.

What do you need to use NTRIP?

To use NTRIP in the field, you need more than just a GNSS receiver. The complete setup normally includes a compatible RTK rover, field software, an internet connection and access to a correction service.

Requirement	Why it matters
RTK-capable GNSS rover	The receiver must be able to use real-time correction data for RTK positioning.
NTRIP client	This may be built into the receiver, controller software, tablet app or machine-control system.
Internet connection	NTRIP needs mobile data, WiFi, a hotspot or another internet connection.
Correction service login	You need the caster address, port, username, password and mountpoint details.
Correct coordinate system	Your field software must use the right coordinate reference system, geoid model and transformation settings.
Good GNSS conditions	Open sky, strong satellite geometry and low multipath improve RTK reliability.

If you are operating your own base station and want to publish its corrections over the internet, you may also need an NTRIP server setup. In many cases this is handled by the base receiver, dedicated software or a correction service platform. For normal rover users, the most important field setup is usually the NTRIP client connection.

What information is needed to configure NTRIP?

Most NTRIP rover setups require a few standard connection details. These are normally provided by the RTK correction service, network operator or project manager. In most field workflows, the user configures the NTRIP client, not the NTRIP server.

• Server or caster address: the internet address of the NTRIP caster that your rover or field software connects to.
• Port: the network port used by the caster.
• Username and password: login details for the correction service.
• Mountpoint: the correction stream you want to use.
• Correction format: usually an RTCM format supported by the receiver.
• Position output settings: such as NMEA output if another system needs position data.

The NTRIP server is usually configured by the correction provider, CORS network operator or the person managing a local base station. For example, if you set up your own GNSS base station and want to send its RTCM corrections to an internet caster, the base station or connected software may act as the NTRIP server. The rover in the field then acts as the NTRIP client.

Some modern field software can load a source table from the caster and show the available mountpoints automatically. In other cases, the user must enter the mountpoint manually.

What is the difference between NTRIP and a UHF radio base station?

NTRIP and UHF radio can both deliver RTK correction data, but they do it in different ways. The best choice depends on your site, internet coverage, required control, baseline length and equipment setup.

Feature	NTRIP correction service	Local base station with UHF radio
Correction delivery	Over the internet	Over radio
Internet required	Yes	No
Base station setup	Often not required by the rover user	Required on or near the project
NTRIP server required	Yes, somewhere in the correction chain, usually operated by the correction provider or base-station manager	No, corrections are transmitted directly by radio from the local base
Typical use	Surveying, GIS, construction layout and mapping in areas with mobile data coverage	Remote sites, private control networks, poor mobile coverage or projects requiring a local base
Range limitation	Depends on correction network coverage, service design and internet connection	Depends on radio power, antenna height, terrain and interference
Control over reference point	Depends on the correction provider or the person managing the base stream	User controls the base position and setup

NTRIP is often convenient because there is no need for the rover user to set up a local base station. However, a local base station can still be the better choice when mobile internet is unreliable, when a project requires a dedicated site control point, or when working far from correction network coverage.

What is Network RTK, CORS and VRS?

NTRIP is often used together with Network RTK, CORS and VRS. These terms describe where the correction data comes from and how it is calculated.

CORS

CORS stands for Continuously Operating Reference Station. A CORS station is a permanent GNSS reference station installed at a known position. It continuously tracks satellite signals and can provide data for RTK correction services, monitoring, geodesy and positioning networks.

Network RTK

Network RTK uses multiple reference stations instead of one local base. The network models errors across a wider area and sends correction data to the rover. This can improve usability across larger regions, provided the rover is inside the supported network area and has a reliable connection.

VRS

VRS stands for Virtual Reference Station. In a VRS workflow, the rover sends its approximate position to the correction network. The system then generates corrections as if there were a reference station close to the rover. This can help reduce distance-related errors compared with using a single far-away reference station.

What does fixed, float and single mean when using NTRIP?

When using NTRIP corrections, your field software will usually show the GNSS solution status. This status tells you how reliable and precise the current position solution is likely to be.

Status	Meaning	Practical interpretation
Single	No RTK correction solution is being used.	The receiver is working like a normal GNSS receiver and accuracy may be much lower.
Float	The rover is using corrections but has not fully resolved the RTK solution.	Accuracy may be improved, but it is usually not suitable for precise survey measurements.
Fixed	The rover has resolved the RTK ambiguity and is using a stable correction solution.	This is normally the desired status for precise RTK surveying and stakeout.

A fixed solution does not automatically guarantee that everything is correct. Surveyors should still check coordinate system settings, known control points, pole height, antenna type, project calibration and site conditions.

Where is NTRIP useful in the field?

NTRIP is useful whenever a professional GNSS rover needs real-time correction data and there is a reliable internet connection. It is especially practical when crews want to work without setting up a local base station every day.

Land surveying

Surveyors use NTRIP for topographic surveys, boundary support work, measured building surveys, as-built checks, control surveys and stakeout. It helps crews start quickly when a reliable correction network is available.

Construction layout

Construction teams use NTRIP-enabled RTK rovers to stake out points, lines, offsets, pads, utilities, roads and site features. It can help reduce setup time compared with a base-rover radio workflow.

GIS and asset mapping

GIS users use NTRIP corrections to improve the position quality of mapped assets such as signs, valves, trees, inspection points, drainage structures and utility features.

Drone mapping ground control

Drone mapping teams can use RTK GNSS rovers with NTRIP to measure ground control points, checkpoints and site features for photogrammetry and LiDAR projects.

Machine control

Machine-control systems may use NTRIP corrections when machines require real-time GNSS positioning and the site has suitable mobile internet coverage. The setup must be checked carefully because machine-control workflows depend heavily on coordinate systems, site models and correction reliability.

Advantages of using NTRIP

NTRIP is popular because it makes RTK correction delivery easier in many working environments. The biggest advantage is convenience: the user can often connect to an existing correction network rather than setting up and guarding a local base station.

• Less equipment to set up on site compared with a base-rover radio setup.
• No local UHF radio range limitation when mobile internet and network coverage are available.
• Useful for crews moving between multiple nearby sites in one day.
• Can support regional RTK workflows through CORS or network RTK services.
• Works well with many modern GNSS receivers, controllers and surveying software packages.
• Can also be used with a private base station when the base correction stream is uploaded through an NTRIP server.

Limitations and things to check before using NTRIP

NTRIP is powerful, but it is not always the best solution for every site. It depends on internet access, correction service coverage, receiver compatibility and correct field configuration.

Mobile data coverage

NTRIP needs a stable internet connection. If the site has weak mobile signal, unstable data or no network coverage, the rover may lose corrections or drop from fixed to float. In these areas, a local base station with radio may be more reliable.

Correction network coverage

Not every correction service covers every region. Before relying on NTRIP, check whether your project is inside the supported service area and whether the network is suitable for the required accuracy.

NTRIP server reliability

If you are using a private base station or a correction provider that depends on uploaded base streams, the NTRIP server must stay online and continue sending correction data to the caster. If the NTRIP server stops, the caster may still be reachable, but the correction stream itself may be unavailable or outdated.

Coordinate systems and transformations

Correction data alone does not solve coordinate system problems. Your field software must be set to the correct coordinate reference system, geoid model, site calibration and project units. A wrong coordinate setup can produce precise-looking but incorrect coordinates.

Receiver and software compatibility

Check that your GNSS receiver and field software can use the selected NTRIP stream and RTCM messages. Some workflows may require specific constellation support, message types or firmware settings.

Mountpoint selection

The mountpoint must match the job requirements. A nearby single-base mountpoint, VRS mountpoint or network RTK mountpoint can produce different results. If you are not sure which mountpoint to use, ask the correction provider or equipment supplier.

Field obstructions

NTRIP cannot remove all GNSS problems. Buildings, trees, metal structures, vehicles, fences and reflective surfaces can still cause multipath or poor satellite visibility. A strong correction stream does not replace good field practice.

Common NTRIP problems and how to troubleshoot them

Problem	Possible cause	What to check
No connection to caster	No internet, wrong server address or blocked port.	Check mobile data, SIM card, APN settings, server address and port.
Login failed	Incorrect username, password or expired subscription.	Re-enter credentials and confirm account status with the provider.
No mountpoints visible	Source table not loading or wrong caster details.	Check caster address, port and internet connection.
Mountpoint visible but no correction data	The NTRIP server may not be sending data to the caster, or the correction stream may be offline.	Check stream status with the correction provider or confirm that the base station and NTRIP server are running.
Corrections received but no fix	Poor sky view, wrong mountpoint, incompatible RTCM stream or long convergence.	Move to open sky, check mountpoint, verify receiver compatibility and wait for a stable solution.
Fixed solution but wrong coordinates	Wrong coordinate system, geoid model, site calibration or base reference.	Measure known control points and verify all project settings.
Frequent dropouts	Unstable mobile data, poor signal coverage or interrupted stream from the NTRIP server.	Use a better SIM, external modem, hotspot, different provider or local base station.

NTRIP setup workflow for a GNSS rover

The exact menu names differ between brands and software packages, but the general workflow is similar for most RTK GNSS systems.

1. Create or open the correct project in your field software.
2. Select the correct coordinate system, geoid model and units.
3. Connect the controller to the GNSS receiver.
4. Set the rover correction mode to NTRIP, network RTK or internet corrections.
5. Enter the caster address, port, username and password.
6. Load the mountpoint list and select the correct correction stream.
7. Start the rover and confirm that correction data is being received.
8. Wait for a stable fixed RTK solution.
9. Measure a known control point before starting production work.
10. Continue checking control points during the survey where required by the project.

How is an NTRIP server setup different from a rover setup?

A rover setup is usually about receiving correction data. An NTRIP server setup is about sending correction data. This distinction is important for surveyors who want to operate their own base station and make corrections available through the internet.

Workflow	Main purpose	Typical user
NTRIP client setup	Receives correction data from a caster for RTK positioning.	Rover user, surveyor, construction layout crew, GIS operator or machine-control user.
NTRIP server setup	Sends correction data from a base station or reference receiver to a caster.	Correction provider, CORS operator, survey company managing a private base stream or site manager.

For many users, the NTRIP server is invisible because it is managed by the correction service. However, when you run your own base station, the NTRIP server becomes important. It must send the correct correction format from the correct base position to the correct caster and mountpoint.

Is NTRIP accurate?

NTRIP itself does not define the accuracy. It only delivers correction data. The final accuracy depends on the GNSS receiver, antenna, correction source, distance to reference stations, network quality, satellite geometry, local obstructions, multipath, coordinate settings and field procedure.

With suitable survey-grade equipment, a reliable correction service and good field conditions, NTRIP is commonly used for centimetre-level RTK work. However, users should always verify results against known control points and follow the accuracy requirements of the project.

Is NTRIP better than setting up your own base station?

NTRIP is not automatically better than a base station. It is better for some workflows and less suitable for others.

NTRIP is often the better choice when there is reliable mobile internet, good correction network coverage and the user wants a fast setup with less equipment. A local base station is often the better choice when working in remote areas, when mobile internet is poor, when the project needs a local site coordinate base, or when the user wants full control over the reference point.

There is also a combined workflow: you can use your own base station and send its corrections over the internet through an NTRIP server and caster. This can be useful when a site needs local control but radio transmission is not practical. The suitability depends on the base receiver, software, internet connection and project requirements.

Many professional surveyors use more than one correction method. They use NTRIP where correction network coverage is strong and switch to a local base-rover setup where site conditions require it.

What should buyers check before choosing an NTRIP-ready GNSS receiver?

When comparing RTK GNSS receivers for NTRIP workflows, do not only look at the receiver price. Check the complete field workflow, including controller, software, connectivity and correction service support.

Buying question	Why it matters
Does the receiver support RTK corrections over the internet?	The rover must be able to receive and use NTRIP correction streams.
Where is the NTRIP client located?	It may run in the receiver, controller, field software, tablet or external modem.
Does the system support your correction provider?	Compatibility with the correction format and mountpoints is essential.
Is mobile data built in?	A built-in modem can simplify the setup, but a controller or hotspot may also be used.
Does the field software handle coordinate systems properly?	Correct coordinate system setup is critical for professional results.
Can the receiver also use UHF radio?	Dual NTRIP and radio capability gives more flexibility across different sites.
Can the receiver work as an NTRIP server if needed?	This matters if you want to use the receiver as a base station and send corrections to an internet caster.

Related Global GPS Systems product categories

Global GPS Systems supplies surveying and construction equipment for different GNSS correction workflows. If you want to use NTRIP in the field, the most relevant categories are RTK GNSS receivers, GPS rover sets, GPS rover-base sets, data collectors, surveying software and correction services.

For many buyers, the best choice is not only the receiver with the strongest specifications on paper. The right setup depends on how you work: one-person surveying, construction layout, GIS mapping, drone ground control, machine control, local base-rover work or network RTK with NTRIP.

FAQ about NTRIP

What does NTRIP stand for?

NTRIP stands for Networked Transport of RTCM via Internet Protocol. It is used to stream GNSS correction data over the internet to receivers, controllers and other positioning systems.

Is NTRIP the same as RTK?

No. RTK is the positioning method used to calculate accurate GNSS coordinates in real time. NTRIP is the internet-based delivery method used to send correction data to the rover.

What is an NTRIP server?

An NTRIP server sends correction data from a GNSS base station, CORS station or reference receiver to an NTRIP caster. The caster then distributes that correction stream to NTRIP clients, such as rovers, field controllers or machine-control systems.

What is an NTRIP caster?

An NTRIP caster is the internet distribution point that receives correction streams from NTRIP servers and makes them available to NTRIP clients. Your rover or field software connects to the caster to receive the selected mountpoint.

What is an NTRIP client?

An NTRIP client is the device or software that connects to the NTRIP caster and receives correction data. In the field, the client may be built into the GNSS receiver, controller software, tablet app or machine-control system.

Do I need internet for NTRIP?

Yes. NTRIP requires an internet connection. This is usually provided by a SIM card, mobile hotspot, controller modem, receiver modem or WiFi connection.

Can I use NTRIP without a base station?

Yes, if you have access to a correction service or CORS network. In that case, you may not need to set up your own local base station. However, the correction service itself still relies on reference station data somewhere in the network.

Can I use my own base station with NTRIP?

Yes. In some workflows, your own base station can send RTCM correction data to an NTRIP caster through an NTRIP server. Your rover then connects to the caster as an NTRIP client. This can be useful when you want local site control but prefer internet-based correction delivery instead of UHF radio.

What is a mountpoint in NTRIP?

A mountpoint is a named correction stream on an NTRIP caster. Different mountpoints may provide different correction types, reference stations, network solutions or message formats.

Does NTRIP work with every GNSS receiver?

No. The receiver, controller and software must support the required NTRIP workflow and correction format. Always check compatibility before choosing a receiver or correction service.

Why does my rover stay in float when using NTRIP?

A rover may stay in float because of poor satellite visibility, multipath, weak correction data, an unsuitable mountpoint, receiver incompatibility, long distance from the correction source or unstable internet. Start by checking open-sky conditions, correction stream settings and coordinate setup.

Why can I connect to the caster but still receive no corrections?

This can happen when the mountpoint is offline, the NTRIP server is not sending correction data to the caster, the selected stream is unavailable or your account does not have access to that mountpoint. Check the mountpoint status and confirm the stream with the correction provider or base-station manager.

Should I use NTRIP or UHF radio for RTK?

Use NTRIP when you have reliable mobile internet and good correction network coverage. Use UHF radio or a local base station when internet coverage is poor, when working remotely or when the project requires full control over the base position.