NTRIP Corrections Explained: Why Your RTK Can Be Wrong | Emlid

Your NTRIP corrections decide whether your RTK data is right, and your receiver can't tell you when they're bad. Igor Vereninov, co-founder and CEO of Emlid, explains at INTERGEO 2026 what goes wrong with NTRIP correction services and how Emlid now builds corrections into every Reach receiver. What you get: Why classic NTRIP setup (register, port number, mount point, pick 1 of 20 options) loses non-surveyors Why a receiver shows FIX and good accuracy even when the base station behind your NTRIP service is bad Michal's scan targets were 20 cm off: the NTRIP service was the problem, not the receiver Who runs the base stations: Emlid Corrections uses Point One Navigation's own monitored network Centimeter-level RTK, vertical roughly 50% above horizontal, and the right datum per country (ETRS89, GDA2020, NAD83) Free crowdsourced NTRIP networks: fine for experiments, not for paid work One year of corrections with every Reach receiver, and what happens after it Made in partnership with Emlid. Igor Vereninov:   / igor-vereninov-52a73ab0   Emlid Corrections: https://emlid.com/rtk-corrections/ #NTRIP #RTK #GNSS Chapters: 0:00 Bad NTRIP corrections on a scanning job 0:46 NTRIP corrections built into every Reach 1:21 Why NTRIP setup loses non-surveyors 2:22 Who runs the base stations 3:48 NTRIP accuracy: horizontal vs. vertical 5:25 The right datum in every country 6:08 Benchmarks and coverage 6:40 20 cm off: receiver or NTRIP? 7:42 Small vs. big receiver accuracy 8:37 Why a FIX can hide bad corrections 9:37 Free crowdsourced NTRIP networks 10:10 What NTRIP costs after the free year 11:34 What's next from Emlid