BVG transport.rest vs OpenVan

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

Uptime · 30d
Uptime · 90d71.6%100%
Uptime · 30d66.7%100%
P50 · ms1106864
P95 · ms44312707
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no auth
Rate limitUnpublished120 req/window · 119 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

BVG transport.rest vs OpenVan: common questions

Which is more reliable, BVG transport.rest or OpenVan?

On our scheduled checks, OpenVan leads on measured uptime — BVG transport.rest at 71.6% versus OpenVan at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, BVG transport.rest or OpenVan?

OpenVan has the lower median latency in our checks — BVG transport.rest responds in 1106 ms versus OpenVan at 864 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 BVG transport.rest and OpenVan need an API key?

Neither needs a paid key — BVG transport.rest is callable with no signup, and OpenVan is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call BVG transport.rest and OpenVan from the browser?

Yes — both BVG transport.rest and OpenVan send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are BVG transport.rest and OpenVan free for commercial use?

BVG transport.rest has unclear commercial terms, and OpenVan has unclear commercial terms. 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.