Details of daily traffic of SNCF trains in Île-de-France (RER and Transiliens)

Open data API in a single place

Provided by AlertesRER

Get early access to Details of daily traffic of SNCF trains in Île-de-France (RER and Transiliens) API!

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

Dataset information

Country of origin
Updated
2020.02.09 21:19
Created
2020.01.18
Available languages
English
Keywords
circulation, rer, ponctualite, transilien, sncf
Quality scoring

Dataset description

## Information For now the data are published manually and at undetermined time intervals. Eventually, they will be published on a daily basis, automatically. ### Description Each line in the file describes a train of the relevant line, where: — **‘year’**: The year that train ran. — **‘month’**: The month that train ran. — **‘day’**: The day that train ran. — **‘day_week’**: Day of the corresponding week, where: — 1 = Monday — 2 = Tuesday —... — 7 = Sunday — **‘numero_week’**: Number of the week of the corresponding year. — **‘est_week’**: If ‘1’, the journey of this train took place on a weekday. ‘0’ otherwise. — **‘est_weekend’**: If ‘1’, the journey of this train took place during the weekend (Saturday or Sunday). ‘0’ if it took place on a weekday. — **‘mission’**: Name of the train mission (example: “AOLO”. — **‘time_depart_prevue’**: Scheduled departure time of this train (in the format ‘HH:mm’, e.g. ‘09h27’). — **‘name_gare_depart’**: Name of the departure station. — **‘id_gare_depart’**: Identifier of the departure station. In general, this identifier is the UIC of this station (in this case the identifier is prefixed by ‘uic_’. Otherwise, it is an internal identifier). — **‘name_gare_arrival’**: Name of the arrival station (unknown for now). — **‘id_gare_arrival’**: Identifier of the arrival station. In general, this identifier is the UIC of this station (in this case the identifier is prefixed by ‘uic_’. Otherwise, it is an internal identifier). — **‘status’**: Indication on the journey of the train: — ‘normal’: The train served all its stops. — ‘partially canceled’: The train did not serve all scheduled stops (the number of unserved stops, called “deleted stops”, is indicated in another column: ‘number_arrets_deleted’). — ‘cancelled’: The train was removed from traffic and therefore did not serve any planned stops. — **‘number_arrets’**: Number of stops planned by this train. — **‘number_arrets_deleted’**: Number of stops not served by this train. — **‘delay_max_en_seconds’**: Maximum delay (in seconds) that this train experienced at one of its stops. — **‘delay_medium_en_seconds’**: Average delay (in seconds) of all stops served by this train. — **‘delay_median_en_seconds’**: Median delay (in seconds) of all stops served by this train. This value means that half of the stops had a delay less than or equal to that value, and the other half a delay greater than or equal to that value. — **‘delay_in_minutes_by_gare’**: Number of minutes late on arrival for each station, separated by the separator ‘-’. If a stop has been deleted, then “/” is indicated. If the train has been removed, then no value is given. For example: ‘1-2 —/— 4’ means that the train: — arrived 1 minute late at its first stop — arrived 2 minutes late at his 2nd stop — did not serve its third judgment — arrived 4 minutes late to his terminus — **‘decrease_delays_in_minutes’**: List of the different delay values encountered (in minutes), with for each of them the number of stops that had this delay. These values shall be expressed in the format <number_of_minutes_delay: number_d_stops_having_known_this_late> and are separated by the separator ‘—’. If the train has been removed, then no value is given. For example: < 0: 1-1: 1-2: 1-3: 3-4: 3-5: 1-7: 2' means that for the 12 stops of this train: — 1 stop was delayed by 0 minutes ('0: 1') — 1 stop was 1 minute late ('1: 1') — 1 stop was delayed by 2 minutes ('2: 1') — 3 stops were delayed by 3 minutes ('3: 3') — 3 stops were 4 minutes late ('4: 3') — 1 stop was 5 minutes late ('5: 1') — 2 stops were 7 minutes late ('7: 2')
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