All states / Alaska
RTK corrections in Alaska
Free 15 options · ACORN (Alaska CORSContinuously Operating Reference Station. A permanent GPS receiver that records satellite data all day, every day.More Network) · Alaska DOTDepartment of Transportation. The state agency that runs many of the free state RTK networks.More&PF · 1 regional/private network(s)
All 15 RTK options in Alaska
Every way to get RTKReal-time kinematic. A way to make GPS accurate to about an inch by getting live corrections from a nearby base station.More CorrectionsLive info from a base station about how far off the satellite signals are, so your rover can cancel out the error.More here, free and paid, side by side: the state network, regional or private networks, and nationwide services.
| Option | Type | Price |
|---|---|---|
| ACORN (Alaska CORS Network) State-run | Free | Free (registration required) |
| Frontier VRS Regional / private | Paid | Not published |
| Point One Navigation Polaris Nationwide | Paid | Virtual RTK $42/mo per license (~10 cm); True RTK $125/mo per license (1-3 cm); annual discounts |
| GEODNET RTK Nationwide | Paid | $40/mo or $400/yr per device |
| RTKdata Nationwide | Paid | $40/mo, $400/yr, or $1,920 for 5 yrs per device |
| E38 RTK Premium Nationwide | Paid | From $100 (shortest term; see page for durations) |
| Emlid Corrections Nationwide | Paid | 1 yr included with eligible Reach receivers; top-up $699/1 yr or $1,199/3 yr per device (via E38) |
| u-blox PointPerfect Flex Nationwide | Paid | From $5.90/mo (up to 100 hrs); 30-day free trial |
| Swift Navigation Skylark Nationwide | Paid | From $69/mo (1 cm RTK) or $29/mo (sub-decimeter RTK-SSR) per ArduSimple |
| Leica (HxGN) SmartNet Nationwide | Paid | Not published |
| Trimble VRS Now Nationwide | Paid | Not published |
| Topcon Topnet Live Nationwide | Paid | $1,800 new US subscription (Topcon store); monthly/project terms via dealers |
| Carlson SkyNet RTN Nationwide | Paid | $1,500/yr; 14-day free trial |
| RTK2GO Nationwide | Free | Free community CasterThe internet server that hands out correction streams. Your rover logs in to it, like tuning into a radio station.More; no quality guarantees |
| NOAA NGS CORS Nationwide | Free | Free post-processing data (RINEXA standard file format for raw GPS data. Any brand of receiver or software can read it.More); not a real-time RTK service |
| NOAA CORS (NCN) | Free Post-processing only | Free |
ACORN (Alaska CORS Network)
Free- Operator
- Alaska DOT&PF
- Access
- Free
- Price
- Free (registration required)
- Coverage
- Alaska
NTRIP caster
hostwww.acorn-gnss.net
PortA number that tells your device which "door" on the caster server to use. For NTRIP it's often 2101.More2101
protocolNTRIP
New find. Coverage is regional (Southcentral, Interior, Southeast VRSVirtual reference station. The network blends nearby stations to create a pretend base right next to you, which keeps the baseline short.More). Free status and caster come from a state presentation; the operator site loads but we didn't read its terms.
PPK with NOAA CORS in Alaska
NOAANational Oceanic and Atmospheric Administration. The US agency that includes NGS and runs the CORS network.More's permanent Base stationA GNSS receiver sitting still on a known spot. It figures out how wrong the satellite signals are right now and shares that as corrections.More record satellite data all day and post it free. You can download those files and use them after a job to correct your drone or rover data (PPK), or to pin down your own base with OPUS. This is not live RTK. This state has 94 working station(s). Each NGSNational Geodetic Survey. The part of NOAA that runs the official US coordinate system, CORS and OPUS.More site log has the station's name and details.
| Station ID | Lat, Lon | NGS links |
|---|---|---|
| AB02 | 52.9706, -168.8547 | Coordinates · Site log |
| AB04 | 63.6569, -170.5674 | Coordinates · Site log |
| AB06 | 54.8853, -163.4235 | Coordinates · Site log |
| AB07 | 55.3493, -160.4768 | Coordinates · Site log |
| AB08 | 60.3848, -166.2009 | Coordinates · Site log |
| AB09 | 65.6150, -168.0621 | Coordinates · Site log |
| AB11 | 64.5645, -165.3735 | Coordinates · Site log |
| AB14 | 59.1082, -159.0915 | Coordinates · Site log |
| AB15 | 61.0397, -159.8784 | Coordinates · Site log |
| AB17 | 63.8864, -160.6947 | Coordinates · Site log |
| AB18 | 66.8584, -162.6135 | Coordinates · Site log |
| AB21 | 51.8642, -176.6627 | Coordinates · Site log |
| AB22 | 59.8993, -154.6983 | Coordinates · Site log |
| AB27 | 67.0559, -156.9049 | Coordinates · Site log |
| AB28 | 62.0938, -152.8149 | Coordinates · Site log |
| AB33 | 67.2510, -150.1726 | Coordinates · Site log |
| AB36 | 65.0304, -150.7440 | Coordinates · Site log |
| AB37 | 62.9673, -145.4519 | Coordinates · Site log |
| AB39 | 66.5593, -145.2126 | Coordinates · Site log |
| AB41 | 64.7773, -141.1581 | Coordinates · Site log |
| AB42 | 59.3404, -138.8988 | Coordinates · Site log |
| AB43 | 58.1988, -136.6408 | Coordinates · Site log |
| AB44 | 59.5280, -135.2283 | Coordinates · Site log |
| AB45 | 68.7605, -148.8712 | Coordinates · Site log |
| AB46 | 68.1207, -145.5679 | Coordinates · Site log |
| AB48 | 56.2451, -134.6470 | Coordinates · Site log |
| AB49 | 55.5801, -133.0685 | Coordinates · Site log |
| AB50 | 58.4168, -134.5453 | Coordinates · Site log |
| AB51 | 56.7976, -132.9136 | Coordinates · Site log |
| AC07 | 65.9613, -161.2866 | Coordinates · Site log |
| AC08 | 58.9288, -153.6447 | Coordinates · Site log |
| AC09 | 59.8685, -144.5239 | Coordinates · Site log |
| AC10 | 54.5226, -164.8867 | Coordinates · Site log |
| AC13 | 55.8219, -155.6224 | Coordinates · Site log |
| AC17 | 60.6639, -152.4039 | Coordinates · Site log |
| AC19 | 62.5192, -153.6073 | Coordinates · Site log |
| AC23 | 60.4751, -150.8780 | Coordinates · Site log |
| AC24 | 58.6816, -156.6528 | Coordinates · Site log |
| AC25 | 55.0890, -162.3141 | Coordinates · Site log |
| AC26 | 58.2146, -154.1503 | Coordinates · Site log |
| AC27 | 59.2525, -154.1629 | Coordinates · Site log |
| AC29 | 59.4296, -146.3400 | Coordinates · Site log |
| AC31 | 64.6380, -162.2391 | Coordinates · Site log |
| AC37 | 60.4397, -153.8654 | Coordinates · Site log |
| AC38 | 57.7537, -153.3419 | Coordinates · Site log |
| AC39 | 58.6097, -152.3941 | Coordinates · Site log |
| AC40 | 56.9303, -158.6186 | Coordinates · Site log |
| AC42 | 54.4718, -162.7836 | Coordinates · Site log |
| AC43 | 59.5213, -149.6287 | Coordinates · Site log |
| AC45 | 56.5645, -154.1810 | Coordinates · Site log |
| AC47 | 60.0814, -152.6240 | Coordinates · Site log |
| AC48 | 60.6459, -147.3430 | Coordinates · Site log |
| AC50 | 65.5538, -164.5666 | Coordinates · Site log |
| AC51 | 61.4981, -151.8354 | Coordinates · Site log |
| AC52 | 57.5673, -157.5742 | Coordinates · Site log |
| AC57 | 61.1386, -145.7427 | Coordinates · Site log |
| AC58 | 57.1561, -170.2178 | Coordinates · Site log |
| AC60 | 52.7146, 174.0763 | Coordinates · Site log |
| AC61 | 64.0293, -142.0759 | Coordinates · Site log |
| AC62 | 63.0836, -146.3127 | Coordinates · Site log |
| AC63 | 63.5024, -145.8473 | Coordinates · Site log |
| AC67 | 57.7907, -152.4254 | Coordinates · Site log |
| AC71 | 64.0493, -145.7136 | Coordinates · Site log |
| AC72 | 63.6951, -145.8877 | Coordinates · Site log |
| AC74 | 63.4644, -148.8073 | Coordinates · Site log |
| AC75 | 62.9993, -149.6088 | Coordinates · Site log |
| AC76 | 63.0400, -143.2588 | Coordinates · Site log |
| AC78 | 63.1135, -142.0279 | Coordinates · Site log |
| AC79 | 59.9979, -147.4031 | Coordinates · Site log |
| AKSE | 60.1325, -149.4365 | Coordinates · Site log |
| AKSI | 57.0489, -135.3390 | Coordinates · Site log |
| ANC2 | 61.1752, -149.9834 | Coordinates · Site log |
| AT01 | 63.4840, -162.0064 | Coordinates · Site log |
| ATW2 | 61.5977, -149.1323 | Coordinates · Site log |
| AV09 | 53.8756, -166.5418 | Coordinates · Site log |
| BET1 | 60.7879, -161.8417 | Coordinates · Site log |
| BRW1 | 71.2828, -156.7899 | Coordinates · Site log |
| CDB8 | 55.1924, -162.7064 | Coordinates · Site log |
| CLGO | 64.8738, -147.8605 | Coordinates · Site log |
| DSL1 | 70.3334, -148.4727 | Coordinates · Site log |
| EDOC | 70.3103, -148.3185 | Coordinates · Site log |
| FAI1 | 64.8096, -147.8473 | Coordinates · Site log |
| FAIR | 64.9780, -147.4992 | Coordinates · Site log |
| GCGO | 64.9781, -147.4994 | Coordinates · Site log |
| GRNX | 63.8355, -148.9782 | Coordinates · Site log |
| JNU1 | 58.3626, -134.5857 | Coordinates · Site log |
| MCES | 59.7461, -151.2578 | Coordinates · Site log |
| OTZ1 | 66.8873, -162.6114 | Coordinates · Site log |
| SELD | 59.4457, -151.7067 | Coordinates · Site log |
| TBON | 61.1797, -149.7851 | Coordinates · Site log |
| TLK2 | 68.6280, -149.5954 | Coordinates · Site log |
| WIKR | 63.5527, -150.9222 | Coordinates · Site log |
| ZAN1 | 61.2292, -149.7802 | Coordinates · Site log |
| ZINA | 61.3835, -143.0241 | Coordinates · Site log |
- Download: daily RINEX files (a standard GPSThe US satellite navigation system. People often use "GPS" to mean all satellite positioning.More file type) at
geodesy.noaa.gov/corsdata/rinex/YYYY/DDD/ssss/or the AWS mirror. Custom time spans are available from UFCORS. - How often it records: after 30 days, NGS thins daily files to one reading every 30 seconds. Full-rate data is available from NOAA NCEI CLASS.
- Set your own base: OPUS. See our OPUS how-to.
Source: NGS CORS data access · station list from NGS ITRFInternational Terrestrial Reference Frame. A worldwide datum. In the US it's about a meter different from NAD 83.More coordinate file (Oct 14, 2026).
Reliability reports
Collecting soonNo user reports yet for Alaska networks. We only show real reports from real users, never sample data. Report collection opens soon, and here's what we'll ask:
Want to be first to report? Use the submit form or subscribe below.
Something wrong or out of date? Report it.