Cambridgeshire Railway Usage Estimates

Open data API in a single place

Provided by Cambridgeshire Insight

Get early access to Cambridgeshire Railway Usage Estimates API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Cambridgeshire Insight catalog

Country of origin

United Kingdom

Updated

2022.11.25 00:00

Created

2019.01.07

Available languages

English

Keywords

rail, transport

Datasource

Official portal for European data link

Quality scoring

Dataset description

<p>A selection of csv files breaking down rail usage estimates across Cambridgeshire and Peterborough. The Office of Rail and Road (ORR) produces yearly (April-March) estimates of the total number of entries, exits and interchanges at rail stations in Great Britain. The estimates are based on ticket sales data recorded in rail industry systems. The complete dataset covers the period 1997-2018.</p> <p><a href="https://dataportal.orr.gov.uk/statistics/usage/estimates-of-station-usage">For subsequent years of railway usage data, you can explore the full national dataset directly from the Office of Rail and Road (ORR) by clicking this link (updated with 2021/22 data on November 24th 2022).:</a></p>

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service