C13 881211 Les Arcs - Draguignan → Menton
Alerts for train 881211
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line C13.
TER 881211 Les Arcs - Draguignan–Menton: final delay under 3 min on 19 of its 29 runs with data in the last 30 days (66%). Median final delay: 0 min. Running now, 10 min late. Expected at Menton: 10:50. TrainsRadar data as of 22 Nov 2026, 10:40 (GMT+1).
An alert on this phone or computer when the 881211 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 10:40
Position estimated from the timetable
Between Monaco-Monte-Carlo and Roquebrune-Cap-Martin +10 min
Estimated arrival at Menton 10:50 10:40 · 46 km/h
- Les Arcs - Draguignan08:27
- Agay08:54
- Mandelieu-la-Napoule09:12
- Biot09:35
- Monaco-Monte-Carlo10:26
- Roquebrune-Cap-Martin10:34
- Menton10:40
Today it is running worse than usual: typical arrival delay is 0 min; 66% of the last 29 runs arrived on time.
Last 30 days
Arrival delay at Menton, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 28 Oct Max en route +70 min · last fix heading to Monaco-Monte-Carlo +70 min
- Sat 17 Oct Max en route +35 min · last fix heading to Monaco-Monte-Carlo +35 min
- Thu 27 Aug Max en route +35 min · last fix heading to StopPoint:OCETrain TER-8775635 +35 min
- Fri 28 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8775636 +30 min
- Fri 13 Nov Max en route +25 min · last fix heading to Menton +25 min
Distribution · 90 days
86 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 59% · 51
- 3–10 min 21% · 18
- 10–30 min 15% · 13
- 30+ min 5% · 4
On-time by weekday
- 64% M n=11
- 69% T n=13
- 46% W n=13
- 50% T n=12
- 54% F n=13
- 67% S n=12
- 67% S n=12
Stops and timetable
Timetable of the latest run from the operator’s GTFS (29 stops).
Last 90 days, 86 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 08:27 | on time | +5 min | Passed | |
| 08:39 / 08:40 | ≈ on time | ≈ +6 min | Passed | |
| 08:43 / 08:44 | ≈ on time | ≈ +6 min | Passed | |
| 08:47 / 08:48 | ≈ on time | ≈ +6 min | Passed | |
| 08:51 / 08:52 | ≈ on time | ≈ +7 min | Passed | |
| 08:54 / 08:55 | ≈ on time | ≈ +7 min | Passed | |
| 08:58 / 08:59 | ≈ on time | ≈ +8 min | Passed | |
| 09:04 / 09:05 | ≈ on time | ≈ +9 min | Passed | |
| 09:09 / 09:10 | ≈ on time | ≈ +9 min | Passed | |
| 09:12 / 09:13 | ≈ on time | ≈ +9 min | Passed | |
| 09:16 / 09:17 | ≈ on time | ≈ +9 min | Passed | |
| 09:20 / 09:22 | ≈ on time | ≈ +10 min | Passed | |
| 09:29 / 09:30 | ≈ on time | ≈ +10 min | Passed | |
| 09:32 / 09:33 | ≈ on time | ≈ +10 min | Passed | |
| 09:35 / 09:36 | ≈ on time | ≈ +10 min | Passed | |
| 09:40 / 09:41 | ≈ on time | ≈ +10 min | Passed | |
| 09:43 / 09:44 | ≈ on time | ≈ +10 min | Passed | |
| 09:47 / 09:48 | ≈ on time | ≈ +11 min | Passed | |
| 09:50 / 09:52 | ≈ on time | ≈ +11 min | Passed | |
| 09:59 / 10:02 | ≈ on time | ≈ +11 min | Passed | |
| 10:05 / 10:07 | ≈ on time | ≈ +12 min | Passed | |
| 10:09 / 10:10 | ≈ on time | ≈ +12 min | Passed | |
| 10:13 / 10:14 | ≈ on time | ≈ +13 min | Passed | |
| 10:18 / 10:19 | ≈ on time | ≈ +13 min | Passed | |
| 10:22 / 10:23 | ≈ on time | ≈ +13 min | Passed | |
| 10:26 / 10:29 | ≈ on time | ≈ +14 min | Passed | |
| 10:34 / 10:35 | ≈ on time | ≈ +14 min | ||
| 10:37 / 10:38 | ≈ on time | ≈ +15 min | ||
| 10:40 | on time | +15 min |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Roquebrune-Cap-Martin 10:39Partial coverage | +10 min | +10 min |
| Sat 21 Nov | Menton 10:39 | 0 min | — |
| Fri 20 Nov | Menton 10:40 | 0 min | — |
| Thu 19 Nov | Menton 10:44 | +5 min | +5 min |
| Wed 18 Nov | Menton 10:40 | 0 min | — |
| Tue 17 Nov | Menton 10:39 | 0 min | — |
| Mon 16 Nov | Menton 10:44 | +5 min | +5 min |
| Sun 15 Nov | Menton 10:39 | 0 min | — |
| Sat 14 Nov | Menton 10:39 | 0 min | — |
| Fri 13 Nov | Menton 11:04 | +25 min | +25 min |
| Thu 12 Nov | Menton 10:39 | 0 min | — |
| Wed 11 Nov | Menton 10:39 | +5 min | +5 min |
| Tue 10 Nov | Menton 10:39 | 0 min | — |
| Mon 9 Nov | Menton 10:41 | 0 min | — |
| Sun 8 Nov | Monaco-Monte-Carlo 10:38 | +10 min | +10 min |
| Sat 7 Nov | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Fri 6 Nov | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Wed 4 Nov | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Tue 3 Nov | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Mon 2 Nov | Monaco-Monte-Carlo 10:38 | +10 min | +10 min |
| Sun 1 Nov | Monaco-Monte-Carlo 10:29 | 0 min | — |
| Sat 31 Oct | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Fri 30 Oct | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Thu 29 Oct | Monaco-Monte-Carlo 10:48 | +20 min | +25 min |
| Wed 28 Oct | Monaco-Monte-Carlo 11:38 | +70 min | +70 min |
| Tue 27 Oct | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Mon 26 Oct | Monaco-Monte-Carlo 10:28 | 0 min | +5 min |
| Sun 25 Oct | Monaco-Monte-Carlo 10:33 | +5 min | +5 min |
| Sat 24 Oct | Monaco-Monte-Carlo 10:28 | 0 min | — |
| Fri 23 Oct | Monaco-Monte-Carlo 10:33 | +5 min | +5 min |