StayingAPI vs Transport for Norway

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms143269
P95 · ms9131737
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseNorwegian Licence for Open Government Data (NLOD)
Free tierFree — open data, no key; ET-Client-Name header requested
Rate limitRate-limited for unidentified consumers (no numeric threshold published)
In directory since2026-09-212026-07-05
operationalpartialdownno data

StayingAPI vs Transport for Norway: common questions

Which is more reliable, StayingAPI or Transport for Norway?

Both are neck-and-neck — StayingAPI and Transport for Norway each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, StayingAPI or Transport for Norway?

StayingAPI has the lower median latency in our checks — StayingAPI responds in 143 ms versus Transport for Norway at 269 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do StayingAPI and Transport for Norway need an API key?

Transport for Norway needs no key, while StayingAPI requires a free API key. If you want to start calling without signup, reach for Transport for Norway first.

Can I call StayingAPI and Transport for Norway from the browser?

Only Transport for Norway is browser-friendly — it returns CORS headers over HTTPS. StayingAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are StayingAPI and Transport for Norway free for commercial use?

StayingAPI has unclear commercial terms, and Transport for Norway allows commercial use on its free tier. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.