Counting up-and-coming passengers on Transilien trains

Open data API in a single place

Provided by SNCF

Get early access to Counting up-and-coming passengers on Transilien trains API!

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

Dataset information

Country of origin
Updated
2025.07.04 12:23
Created
2025.07.04
Available languages
English
Keywords
transilien, comptage-et-flux, montants, comptage, ile-de-france
Quality scoring

Dataset description

Counting of up-and-coming passengers on Transilien trains by time slot. These manual counts are carried out every three to four years and count the number of amounts for: * Each train on a Transilien line at each station served * Each typical day (JOB, Saturday and Sunday), excluding work and school holidays Explanation of the wording used: * Station name: name of station * Station code: UIC code. It is unique and allows the identification of the station * Type of day: specify the day of counting: Saturday, Sunday or JOB (Tuesday or Thursday) * Counting date: Specifies the date of counting * Line: specifies the line of the train concerned when counting because some stations are served by several lines. In this case, the details are given, as in the example of the Juvisy station. * Time slot: time slot associated with the time of arrival of the train at the station * Amounts: indicates the number of amounts in trains according to the above criteria Last update of the file: 24 March 2020 With each update, we cancel and replace the database: there is no historization of counts. For a given station, there may be several counting dates: \- Two lines passing through the same station are not necessarily counted on the same day; \- And/or there may be catch-up days if the first day of counting is incomplete. Thus, to have the number of reference amounts, it is necessary to keep all the data to have the completeness of the counts. Attention points: \- Line C was interrupted on Saturday and Sunday of the counting of Line D in Juvisy. Line D amounts at Juvisy station on Saturdays and Sundays are therefore increased by carry-overs of Line C amounts. \- Addition of an ‘Axis’ column to identify axes in the same row that were not counted on the same date
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.

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

Copyright © 2026. Made by Apitalks