Train NS 7090 Almelo – Apeldoorn

Almelo 00:05 → Apeldoorn 00:52 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:00 +6 min

  1. Almelo00:05
  2. Wierden00:10
  3. Holten00:21
  4. Deventer Colmschate00:31
  5. Deventer00:36
  6. Apeldoorn Osseveld00:47
  7. Apeldoorn00:52

Next service: tomorrow 00:05 from Almelo · Sun 15 Nov

Next departure 00:05 tomorrow · Almelo
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 3 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Worst days

  • Sat 14 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=5
  • 100% W n=6
  • 100% T n=5
  • 100% F n=3
  • 83% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 29 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
00:05on time on time
00:10≈ on time ≈ on time
00:16≈ on time ≈ on time
00:21≈ on time ≈ on time
00:31≈ on time ≈ on time
00:36 / 00:37≈ on time ≈ on time
00:42≈ on time ≈ on time
00:47≈ on time ≈ on time
00:52on time on time

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
Sat 14 Nov— 01:00+6 min+6 min
Fri 13 Nov— 00:370 min—
Thu 12 Nov— 00:370 min—
Wed 11 Nov— 00:370 min—
Tue 10 Nov— 00:380 min—
Sun 8 NovDeventer Colmschate 00:440 min—
Sat 7 Nov— 00:54+1 min+1 min
Fri 6 Nov— 00:37No data—
Thu 5 Nov— 00:380 min—
Wed 4 Nov— 00:380 min—
Sun 1 NovDeventer Colmschate 00:440 min—
Sat 31 Oct— 00:530 min—
Thu 29 Oct— 00:37No data—
Wed 28 Oct— 00:370 min—
Tue 27 Oct— 00:390 min—
Sun 25 OctDeventer Colmschate 00:45No data—
Sat 24 Oct— 00:540 min—
Fri 23 Oct— 00:400 min—
Thu 22 Oct— 00:370 min—
Wed 21 Oct— 00:370 min—
Tue 20 Oct— 00:380 min—
Sun 18 OctDeventer Colmschate 00:450 min—
Sat 17 OctHolten 00:420 min—
Fri 16 Oct— 01:070 min—
Thu 15 Oct— 01:460 min—
Wed 14 Oct— 00:380 min—
Tue 13 Oct— 01:520 min—
Sun 11 OctDeventer Colmschate 00:470 min—
Sat 10 Oct— 00:56+2 min+2 min
Thu 8 Oct— 00:370 min+1 min