R21 7036 Neuchâtel → Buttes

View line R21

Neuchâtel 10:13 → Buttes 10:55 Daily 0 h 42 min · 12 stops transN

R21 7036 Neuchâtel–Buttes: final delay under 3 min on 9 of its 9 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:12 (GMT+1).

✓ Today’s run finished

Today it reached Buttes at 10:55 0 min

  1. Neuchâtel10:13
  2. Auvernier10:19
  3. Champ-du-Moulin10:28
  4. Travers10:38
  5. La Presta Mines d'asphalte10:41
  6. Môtiers NE10:47
  7. Buttes10:55

Next service: tomorrow 10:13 from Neuchâtel · Mon 23 Nov

Next departure 10:13 tomorrow · Neuchâtel
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 21 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Buttes, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 4 Oct Max en route +39 min · last fix heading to Buttes +39 min

Distribution · 90 days

15 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 7% · 1

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • 100% T n=1
  • — F n=0
  • 100% S n=7
  • 86% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 15 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.

StopSched.Usually 9 days in 10
10:13on time on time
10:16≈ on time ≈ on time
10:19≈ on time ≈ on time
10:22 / 10:23≈ on time ≈ on time
10:28 / 10:29≈ on time ≈ on time
10:34≈ on time ≈ +1 min
10:38 / 10:39≈ on time ≈ +1 min
10:41≈ on time ≈ +1 min
10:43 / 10:44≈ on time ≈ +1 min
10:47≈ on time ≈ +1 min
10:50 / 10:51≈ on time ≈ +2 min
10:55on time +2 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

DateLast stopFinalMax
Sun 22 NovButtes 10:540 min—
Sat 21 NovButtes 10:540 min—
Fri 20 NovButtes 10:54No data—
Thu 19 NovButtes 10:54No data—
Wed 18 NovButtes 10:54No data—
Tue 17 NovButtes 10:54No data—
Mon 16 NovButtes 10:54No data—
Sun 15 NovButtes 10:540 min—
Sat 14 NovButtes 10:54+1 min—
Fri 13 NovButtes 10:54No data—
Thu 12 NovButtes 10:54No data—
Wed 11 NovButtes 10:54No data—
Tue 10 NovButtes 10:54No data—
Mon 9 NovButtes 10:54No data—
Sun 8 NovButtes 10:540 min—
Sat 7 NovButtes 10:540 min—
Fri 6 NovButtes 10:54No data—
Thu 5 NovButtes 10:54No data—
Wed 4 NovButtes 10:54No data—
Tue 3 NovButtes 10:54No data—
Mon 2 NovButtes 10:54No data—
Sun 1 NovButtes 10:560 min—
Sat 31 OctButtes 10:57+1 min+2 min
Fri 30 OctButtes 10:56No data—
Thu 29 OctButtes 10:56No data—
Wed 28 OctButtes 10:56No data—
Tue 27 OctButtes 10:56No data—
Mon 26 OctButtes 10:57No data—
Sun 25 OctButtes 10:56No data—
Sat 24 OctButtes 10:560 min—