From 00:07 on 26 Aug 2026
Scheduled departures
N98HolbornMetroline TravelPlanned00:36Observed— N83HanwellMetroline TravelPlanned00:51Observed— N98HolbornMetroline TravelPlanned01:06Observed— N83HanwellMetroline TravelPlanned01:21Observed— N98HolbornMetroline TravelPlanned01:36Observed— N83HanwellMetroline TravelPlanned01:51Observed— N98HolbornMetroline TravelPlanned02:05Observed— N83HanwellMetroline TravelPlanned02:21Observed— N98HolbornMetroline TravelPlanned02:35Observed— N83HanwellMetroline TravelPlanned02:51Observed— N98HolbornMetroline TravelPlanned03:05Observed— N83HanwellMetroline TravelPlanned03:21Observed— N98HolbornMetroline TravelPlanned03:35Observed— N83HanwellMetroline TravelPlanned03:51Observed— N98HolbornMetroline TravelPlanned04:06Observed— N83HanwellMetroline TravelPlanned04:21Observed— N98HolbornMetroline TravelPlanned04:38Observed— N83HanwellMetroline TravelPlanned04:51Observed— N98HolbornMetroline TravelPlanned05:09Observed— N83HanwellMetroline TravelPlanned05:21Observed— 302Kensal RiseMetroline TravelPlanned08:30Observed— 302Kensal RiseMetroline TravelPlanned08:40Observed— 302Kensal RiseMetroline TravelPlanned08:49Observed— 302Kensal RiseMetroline TravelPlanned08:57Observed— 302Kensal RiseMetroline TravelPlanned09:06Observed— 302Kensal RiseMetroline TravelPlanned15:45Observed— 83AlpertonMetroline TravelPlanned15:53Observed— 302Kensal RiseMetroline TravelPlanned15:55Observed— 83AlpertonMetroline TravelPlanned16:02Observed— 302Kensal RiseMetroline TravelPlanned16:05Observed— 83AlpertonMetroline TravelPlanned16:11Observed— 302Kensal RiseMetroline TravelPlanned16:14Observed— 83AlpertonMetroline TravelPlanned16:20Observed— 302Kensal RiseMetroline TravelPlanned16:24Observed— 83AlpertonMetroline TravelPlanned16:29Observed— 302Kensal RiseMetroline TravelPlanned16:33Observed— 83AlpertonMetroline TravelPlanned16:38Observed— 302Kensal RiseMetroline TravelPlanned16:43Observed— 83AlpertonMetroline TravelPlanned16:47Observed— 302Kensal RiseMetroline TravelPlanned16:52Observed— 83AlpertonMetroline TravelPlanned16:56Observed— 302Kensal RiseMetroline TravelPlanned17:02Observed— 83AlpertonMetroline TravelPlanned17:05Observed— 302Kensal RiseMetroline TravelPlanned17:10Observed— 83AlpertonMetroline TravelPlanned17:14Observed— 302Kensal RiseMetroline TravelPlanned17:19Observed— 83AlpertonMetroline TravelPlanned17:23Observed— 302Kensal RiseMetroline TravelPlanned17:28Observed— 83AlpertonMetroline TravelPlanned17:32Observed— 302Kensal RiseMetroline TravelPlanned17:37Observed— 83AlpertonMetroline TravelPlanned17:41Observed— 302Kensal RiseMetroline TravelPlanned17:46Observed— 83AlpertonMetroline TravelPlanned17:50Observed— 83AlpertonMetroline TravelPlanned17:59Observed— 83AlpertonMetroline TravelPlanned18:08Observed— 83AlpertonMetroline TravelPlanned18:17Observed— 302Kensal RiseMetroline TravelPlanned18:24Observed— 83AlpertonMetroline TravelPlanned18:26Observed— 83AlpertonMetroline TravelPlanned18:35Observed— 83AlpertonMetroline TravelPlanned18:44Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.