Detour Route 52 South: Route 52 diverted from Eastern to Deschênes.+1 more notice

No 52 trips cancelled now · 3 did not run in novembroCancellations →

Previous measure: 54,9% of arrivals were within five minutes of the timetable (38.425 arrivals over 22 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

Linha 52 da STO: Des Cèdre/Rivermead/Vanier

Sentido Pob Allum1 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

KATIMAVIK/DU PLATEAU30 min sched.
de SÉTO/KATIMAVIK31 min sched.
VANIER/ATTIKAMEKS34 min sched.
MCCONNELL/MORLEY-WALTERS35 min sched.
MCCONNELL/CASTELBEAU35 min sched.
MCCONNELL/JEAN-DE LA FONTAINE36 min sched.
MCCONNELL/des MANOIRS36 min sched.
RIVERMEAD/ÉMILE-ZOLA37 min sched.
RIVERMEAD/JEAN-DE LA FONTAINE38 min sched.
PARC-O-BUS RIVERMEAD39 min sched.
chemin d'AYLMER/de l'HIPPODROME42 min sched.
chemin d'AYLMER/MORLEY-WALTERS43 min sched.
VANIER/LYNN44 min sched.
VANIER/CRESCENT44 min sched.
VANIER/des VÉTÉRANS45 min sched.
VANIER/CRESCENT45 min sched.
VANIER/CALVADOS46 min sched.
VANIER/de LUCERNE46 min sched.
CÔTÉ/LUCERNE47 min sched.
CÔTÉ/DESCHÊNES47 min sched.
CÔTÉ/LAMOUREUX48 min sched.
LAMOUREUX/VANIER48 min sched.
VANIER/MADAIRE49 min sched.
VANIER/SAINT-MÉDARD49 min sched.
de LUCERNE/GARDEN50 min sched.
de LUCERNE/VICTOR-BEAUDRY51 min sched.
de LUCERNE/FRASER52 min sched.
de LUCERNE/EASTERN53 min sched.
de LUCERNE/RIESLING54 min sched.
de LUCERNE/ÉLIZABETH56 min sched.
FRANK-ROBINSON/CENTRE WESTERN QUÉBEC56 min sched.
FRANK-ROBINSON/DU PATRIMOINE58 min sched.
PRINCIPALE/WILFRID-LAVIGNE58 min sched.
chemin d'AYLMER/du BORDEAUX59 min sched.
de la COLLINE/chemin d'AYLMER0 min sched.
de la COLLINE/des EXPLORATEURS0 min sched.
de la COLLINE/du VALLON1 min sched.
du VALLON/des DRAVEURS2 min sched.
du VALLON/du CAVEAU3 min sched.
du CAVEAU/SAMUEL-EDEY3 min sched.
SAMUEL-EDEY/des PAYSANS4 min sched.
SAMUEL-EDEY/MCCONNELL5 min sched.
des ALLUMETTIÈRES/SAMUEL-EDEY5 min sched.
WILFRID-LAVIGNE/des ALLUMETTIÈRES7 min sched.
WILFRID-LAVIGNE/des PINACÉES8 min sched.
WILFRID-LAVIGNE/du BOIS-FRANC8 min sched.
WILFRID-LAVIGNE/des THUYAS9 min sched.
WILFRID-LAVIGNE/MAURICE-DUPLESSIS9 min sched.
WILFRID-LAVIGNE/LYSE-DANIELS10 min sched.
WILFRID-LAVIGNE/KLOCK10 min sched.
du RATON-LAVEUR/de la MARMOTTE12 min sched.
du RATON-LAVEUR/du LOUP-GRIS13 min sched.
du RATON-LAVEUR/FRONT13 min sched.
FRONT/du RENARD14 min sched.
FRONT/du MARCHÉ14 min sched.
FRONT/du VERGER15 min sched.
FRONT/des ALLUMETTIÈRES15 min sched.
des ALLUMETTIÈRES/FRONT15 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée18 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 28 de out. de 2026 – 3 de nov. de 2026

Scheduled trips with cancellation notices

Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 2.

Trips needing investigation

4 of 218 trips with a usable feed window (1,8%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

214 with position · 4 to investigate · 34 excluded · 252 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 4 de nov. de 2026, 13:22.

Coverage, exclusions and sources

0 of 8 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

34 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 214 / 252 (84,9%). This is not a delivered-service rate. 7 service days in this source.

Timetables retained before the service day: 7 / 7 requested days · 0 missing days.

Historical calculation: 4 de nov. de 2026, 12:08

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

What does the evidence show?

Predictions against the timetable

54,9%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 38.425
Weekdays with evidence: 17
Evidence window: 6 de out. de 2026 – 3 de nov. de 2026

The hours we have evidence for

05100% · 41 predictions · 6 days
0668% · 951 predictions · 10 days
0756% · 850 predictions · 9 days
0854% · 920 predictions · 10 days
0954% · 1.055 predictions · 11 days
1065% · 1.147 predictions · 11 days
1151% · 1.224 predictions · 12 days
1254% · 1.294 predictions · 12 days
1362% · 1.345 predictions · 12 days
1457% · 1.209 predictions · 13 days
1552% · 1.249 predictions · 12 days
1646% · 1.109 predictions · 12 days
1747% · 1.117 predictions · 12 days
1846% · 1.079 predictions · 11 days
1945% · 1.205 predictions · 11 days
2043% · 1.076 predictions · 10 days
2165% · 1.126 predictions · 10 days
2280% · 1.183 predictions · 10 days
2372% · 1.069 predictions · 10 days

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: 4 de nov. de 2026

6 partial-capture days not counted.

What about time of day?

19 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.

Improvement or decline requires comparable periods. This single result cannot establish a trend.

Explore the dated evidence Source of this result

Ônibus chegando juntos

Last 28 days, 7 de outubro de 2026 to 3 de novembro de 2026: 21 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 8 de outubro de 2026, 12 de outubro de 2026.

Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.

Como isso é medido →How we got this numberComboios de ônibus e pontos lentos em todas as linhas →

Onde esta linha é mais lenta

Slowest: PARC-O-BUS ALLUMETTIÈRES to FRONT/des ALLUMETTIÈRES, 5,1 km/h actual against 16,7 km/h planned.

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos lentos
PARC-O-BUS ALLUMETTIÈRES	FRONT/des ALLUMETTIÈRES	830 m	16,7 km/h	5,1 km/h	223	76%
KATIMAVIK/DU PLATEAU	VANIER/ATTIKAMEKS	970 m	13,5 km/h	7,9 km/h	194	49%
de LUCERNE/FRASER	VANIER/SAINT-MÉDARD	2,2 km	22,9 km/h	12,1 km/h	298	76%
PARC-O-BUS RIVERMEAD	chemin d'AYLMER/MORLEY-WALTERS	790 m	11,8 km/h	14,8 km/h	281	2%
MCCONNELL/MORLEY-WALTERS	VANIER/de SETO	990 m	16,2 km/h	16,2 km/h	288	7%
FRONT/des ALLUMETTIÈRES	PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée	830 m	15,6 km/h	16,5 km/h	299	2%
chemin d'AYLMER/MORLEY-WALTERS	de LUCERNE/FRASER	4,6 km	30,4 km/h	17,3 km/h	282	66%
PARC-O-BUS RIVERMEAD	MCCONNELL/MORLEY-WALTERS	1,7 km	16,7 km/h	18,8 km/h	278	3%

Um trajeto lento levou pelo menos 1.5 vez o tempo previsto.

Como isso é medido →

Cancelamentos nesta linha

O que estas palavras significam →

6 partial-capture days not counted.

6 scheduled trips with counted cancellation notices from qua., 7 de out. to ter., 3 de nov..

Not counted: 2 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Horas com mais cancelamentos: 16 (2), 18 (2), 09 (1)

Últimos trajetos cancelados

sex., 30 de out., scheduled 20:00
ter., 27 de out., scheduled 18:00
sex., 23 de out., scheduled 16:59
ter., 20 de out., scheduled 18:00
ter., 20 de out., scheduled 09:00

Uma causa só aparece quando o alerta da STO para aquele trajeto a informa.

Did not come (no bus seen, no notice), last 7 days: 3 of 218 trips we could check.

Quando esta linha costuma ficar cheia

Com base no nível de lotação informado pelos ônibus da STO nas últimas oito semanas. Um horário é marcado como geralmente cheio quando pelo menos metade das viagens com leitura chegou a ter pessoas em pé ou mais lotação.

Nenhum horário do dia costumou ficar cheio nas últimas oito semanas.

Quando esta linha costuma ficar cheia	Dias úteis	Aos sábados	Aos domingos
Antes das 6 h	Geralmente há lugares0% of 58 trips	Leituras insuficientes	Leituras insuficientes
6h às 9h	Geralmente há lugares0% of 236 trips	Geralmente há lugares0% of 51 trips	Geralmente há lugares0% of 48 trips
9 h às 3 da tarde	Geralmente há lugares0% of 474 trips	Geralmente há lugares0% of 102 trips	Geralmente há lugares0% of 101 trips
3 às 6 pm	Geralmente há lugares1,3% of 226 trips	Geralmente há lugares0% of 61 trips	Geralmente há lugares0% of 67 trips
6 a 10 pm	Geralmente há lugares0,6% of 361 trips	Geralmente há lugares0% of 75 trips	Geralmente há lugares0% of 65 trips
Após as 10 pm	Geralmente há lugares0% of 126 trips	Geralmente há lugares2,2% of 46 trips	Geralmente há lugares0% of 34 trips

Based on 56 computed days.

Fonte: o status de ocupação no feed público de veículos em tempo real da STO. A STO define esse status a partir do sensor de carga de cada ônibus (assentos disponíveis com menos de 60% de lotação, lugares em pé abaixo de 90%, lotado acima de 90%).
Cada trajeto conta uma vez por período do dia, com a maior lotação que ele informou.
Os relatos de ônibus vazio ficam de fora, porque os registros mais antigos não distinguiam um ônibus vazio de um ônibus sem sensor.
Um horário do dia precisa de pelo menos 12 trajetos em pelo menos 4 dias diferentes para ser exibido. Os feriados são contados como o dia da semana em que caem.

Abrir a análise das previsões com datas

Veredicto

What this route needs

Median provider predictions are 3,9 to 5,1 min later than the timetable in 13 hours of the day.

The prediction difference from the timetable grows by about 3,7 min along the route.

Wide prediction spread 08:00 to 11:00, 15:00 to 18:00: the 95th percentile is 26,6 min later than the median.

Scenario: 4 to 5 min more running time on 198 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 20 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 100% of final predictions within five minutes of the timetable, 41 predictions, typically 0,2 min early
06:00: 67,9% of final predictions within five minutes of the timetable, 951 predictions, typically 2,7 min late
07:00: 56% of final predictions within five minutes of the timetable, 850 predictions, typically 4 min late
08:00: 54,1% of final predictions within five minutes of the timetable, 920 predictions, typically 3,2 min late. Provider predictions have a wide spread.
09:00: 54,2% of final predictions within five minutes of the timetable, 1.055 predictions, typically 3,9 min late. Provider predictions have a wide spread.
10:00: 64,5% of final predictions within five minutes of the timetable, 1.147 predictions, typically 2 min late. Provider predictions have a wide spread.
11:00: 51,4% of final predictions within five minutes of the timetable, 1.224 predictions, typically 4,8 min late
12:00: 53,7% of final predictions within five minutes of the timetable, 1.294 predictions, typically 4,3 min late
13:00: 61,8% of final predictions within five minutes of the timetable, 1.345 predictions, typically 3,2 min late
14:00: 56,9% of final predictions within five minutes of the timetable, 1.209 predictions, typically 4 min late
15:00: 51,7% of final predictions within five minutes of the timetable, 1.249 predictions, typically 4,7 min late. Provider predictions have a wide spread.
16:00: 45,7% of final predictions within five minutes of the timetable, 1.109 predictions, typically 5,8 min late. Provider predictions have a wide spread.
17:00: 46,9% of final predictions within five minutes of the timetable, 1.117 predictions, typically 6,7 min late. Provider predictions have a wide spread.
18:00: 45,8% of final predictions within five minutes of the timetable, 1.079 predictions, typically 5,9 min late
19:00: 45,4% of final predictions within five minutes of the timetable, 1.205 predictions, typically 5,3 min late
20:00: 43,4% of final predictions within five minutes of the timetable, 1.076 predictions, typically 5,5 min late
21:00: 64,9% of final predictions within five minutes of the timetable, 1.126 predictions, typically 2,9 min late
22:00: 79,5% of final predictions within five minutes of the timetable, 1.183 predictions, typically 1,8 min late
23:00: 72,1% of final predictions within five minutes of the timetable, 1.069 predictions, typically 2,8 min late

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Quando	Medido	Scenario or next investigation
ProblemPredictions later than timetable	07:00 to 10:00 · 11:00 to 21:00	3,9 min late · 5,1 min late	More running time
ProblemWide prediction spread	08:00 to 11:00 · 15:00 to 18:00	22,8 min swing · 26,6 min swing	Operations, not the timetable

Measurements

Predictions later than timetable · 11:00 to 21:00: Measured arrivals 11.907; Hours affected 10; Spread 16 min; Median delay 5,1 min; Suggested running time change 5,1 min
Wide prediction spread · 15:00 to 18:00: Measured arrivals 3.475; Hours affected 3; Spread 26,6 min; Median delay 5,8 min; Suggested running time change 5,8 min
Predictions later than timetable · 07:00 to 10:00: Measured arrivals 2.825; Hours affected 3; Spread 22,8 min; Median delay 3,9 min; Suggested running time change 3,9 min
Wide prediction spread · 08:00 to 11:00: Measured arrivals 3.122; Hours affected 3; Spread 22,8 min; Median delay 3,2 min; Suggested running time change 3,2 min

Abrir histórico, fiabilidade e análise da rota

Verificação da linha

How route 52 has been running

Um resumo curto do que sabemos. Dizemos isso quando não podemos responder a uma pergunta.

Em resumo

As previsões do provedor ficaram muitas vezes longe do horário nesta amostra datada.

55 in 100 eligible predictions were within 5 minutes of the timetable · 38.425 predictions checked

Tamanho da amostra de previsão: Amostra maior

Based on 38.425 eligible provider predictions over 22 measured days, from 6 de out. de 2026 to 3 de nov. de 2026.

Updated 4 de nov. de 2026, 12:32

Onde e quando as previsões diferiram repetidamente?

Estas são diferenças repetidas entre a previsão e o horário, não falhas de serviço medidas de forma independente. Usam as mesmas previsões elegíveis do resultado acima, mas agrupam por parada, e não por hora. Por isso, as listas podem não coincidir linha por linha.

20–21: 57 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.076 predictions over 10 days).
19–20: 55 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.205 predictions over 11 days).
16–17: 54 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.109 predictions over 12 days).
18–19: 54 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.079 predictions over 11 days).

2 current notices affect this route

• Detour Route 52 South
• Detour Route 52 North

Diferenças de previsão por parada

de la COLLINE/des EXPLORATEURS
84 in 100 eligible predictions differed from the timetable by more than 5 minutes (344 predictions over 24 days).
Abrir esta parada
de LUCERNE/EASTERN
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (346 predictions over 24 days).
Abrir esta parada
de LUCERNE/RIESLING
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 predictions over 24 days).
Abrir esta parada
de la COLLINE/du VALLON
81 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 predictions over 24 days).
Abrir esta parada

São previsões do fornecedor específicas da linha, comparadas com o horário. Elas mostram diferenças repetidas de previsão em um lugar e horário, não chegadas medidas nem a causa delas.

Verificar cada viagem e data

Abra um período para ver cada dia de serviço, trajeto previsto no horário, falha nos dados, ID público de veículo observado e os números exatos por trás deste resumo.

O que os passageiros querem saber

Alguma viagem está cancelada agora?: 0 of 8Verifica as viagens que começam nos terminais da linha nas próximas 4 horas. Não é uma taxa histórica de cancelamento.
Possíveis faltas de ônibus após verificar falhas no feed?: 4 of 218 checked trips need a closer look4 of 218 trips with enough public-feed evidence had no matching position over 7 days. 34 of 252 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Como as previsões do fornecedor diferiram do horário?: At the 95th percentile, the predicted difference was 20,9 min (positive means later; negative means earlier)55 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Qual espera as previsões do provedor indicavam?: Nenhum resultado por linha atinge ainda o limite de dados probantes. Isso não significa que não houve falhas.

Verificação da mudança de horário

Horário publicado: antes e depois

Isto compara o horário oficial atual guardado com a versão anterior guardada. As mudanças de horário são fatos sobre o que foi planejado. Elas não provam que um trajeto foi realizado.

Current published schedule began 2 de novembro de 2026

Dia de serviço selecionado em cada horário publicado

Verificamos a primeira segunda-feira depois do início do novo horário e a segunda-feira uma semana antes. Todos os números vêm das versões oficiais do GTFS guardadas, indicadas abaixo.

Pelo menos uma data escolhida tem serviço incluído ou removido por data do calendário. Considere isso como contexto de feriado ou de serviço especial, não como aumento normal de dia útil.

Antes

Data de serviço verificada: 26 de outubro de 2026

Viagens programadas: 0
Paradas previstas distintas: 0
Percursos publicados distintos: 0
Período de serviço publicado: —–—

Impressão digital do feed: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

Novo horário

Data de serviço verificada: 2 de novembro de 2026

Viagens programadas: 36
Paradas previstas distintas: 122
Percursos publicados distintos: 2
Período de serviço publicado: 5:53–23:45

Operator calendar-date records: 1 added · 0 removed

Impressão digital do feed: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

O serviço melhorou depois da mudança?

Vamos comparar as chegadas confirmadas nos 14 dias antes e depois da mudança. Só publicamos a comparação quando os dois períodos tiverem pelo menos 7 dias de serviço e 200 chegadas.

Still collecting: before has 21.400 arrivals over 13 days; after has 2.624 arrivals over 2 days. No improvement or decline is claimed yet.

Os checksums permitem que qualquer pessoa verifique qual horário guardado gerou as contagens. Uma contagem alterada não indica a causa, um cancelamento, uma decisão da operadora ou um impacto para os passageiros.

Como esta linha é avaliada: Linha regular com todas as paradas

Comparamos a última previsão válida do provedor para cada chegada prevista no horário com o horário oficial. Não são chegadas medidas de forma independente. Um resultado precisa de pelo menos 200 previsões válidas. Dentro de 5 minutos é a meta usada aqui, do ponto de vista do passageiro.

O que estes dados não podem provar

Os dados públicos não trazem contagens confiáveis de passageiros nem registros de passageiros deixados na parada. A falta de uma posição não prova, por si só, um cancelamento, uma ausência de viagem, um retorno antecipado ou uma causa.

Veja as definições, os limites e a ordem dos dados probantes

Feed oficial atual: cancelamentos explícitos, paradas puladas e avisos ativos.
Observações correspondentes: posições de veículos e previsões consolidadas ligadas ao horário oficial.
Horário oficial: o que foi planejado, separado do que foi observado.
Relatos de passageiros e de exploradores: pistas sobre linhas, horários e locais a investigar, não prova numérica por si só.

Resultados provisórios, dados probantes publicados

Como as previsões se compararam com o horário?

A cada hora, comparamos a última previsão válida do provedor para uma chegada prevista no horário com o quadro de horários. “Em até 5 minutos” descreve a diferença entre as previsões. Não é uma chegada medida nem prova de que um ônibus circulou.

Período dos dados probantes: 6 de outubro de 2026 to 3 de novembro de 2026

Até 5 minutos do horário programado: 54,9%
Previsões elegíveis verificadas: 38.425
Dias úteis com dados: 17
Atraso previsto no percentil 95: 20,9 min late

Patterns by hour (20)

Patterns by hour (20)
Hora	Pontual	Mediana	Percentil 95	Evidências
00:00	35,0%	6,8 min late	19 min late	60 · 2 days
05:00	100,0%	0,2 min early	3,2 min late	41 · 6 days
06:00	67,9%	2,7 min late	12,7 min late	951 · 10 days
07:00	56,0%	4 min late	20,8 min late	850 · 9 days
08:00	54,1%	3,2 min late	36,4 min late	920 · 10 days
09:00	54,2%	3,9 min late	26,7 min late	1.055 · 11 days
10:00	64,5%	2 min late	24,3 min late	1.147 · 11 days
11:00	51,4%	4,8 min late	20,9 min late	1.224 · 12 days
12:00	53,7%	4,3 min late	17,5 min late	1.294 · 12 days
13:00	61,8%	3,2 min late	16,8 min late	1.345 · 12 days
14:00	56,9%	4 min late	20,3 min late	1.209 · 13 days
15:00	51,7%	4,7 min late	27,3 min late	1.249 · 12 days
16:00	45,7%	5,8 min late	33,8 min late	1.109 · 12 days
17:00	46,9%	6,7 min late	33,3 min late	1.117 · 12 days
18:00	45,8%	5,9 min late	21,9 min late	1.079 · 11 days
19:00	45,4%	5,3 min late	18,5 min late	1.205 · 11 days
20:00	43,4%	5,5 min late	16,5 min late	1.076 · 10 days
21:00	64,9%	2,9 min late	14,8 min late	1.126 · 10 days
22:00	79,5%	1,8 min late	16,3 min late	1.183 · 10 days
23:00	72,1%	2,8 min late	12 min late	1.069 · 10 days

16 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Ônibus previsto no horário, mas não observado em tempo real

214 / 252 scheduled trips published at least one position across 5 service days (84,9%).

23:004 / 9 trips without a position55,6%
05:002 / 5 trips without a position60,0%
20:005 / 14 trips without a position64,3%
21:004 / 14 trips without a position71,4%
22:004 / 14 trips without a position71,4%
19:005 / 19 trips without a position73,7%

Isto não é uma falta confirmada. Uma posição ausente pode indicar um ônibus cancelado ou perdido. Também pode indicar um ID de trajeto não atribuído ou uma falha no feed da operadora. O Otranspo publica essa lacuna porque ela importa para os passageiros, sem tirar conclusões que os dados não permitem.

Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Fontes e limitações.

Dated service

Trips scheduled that day

The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.

Service day

November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 36 trips in the retained timetable · retained notices; capture coverage unverified

In short: 30 with a matched position · 0 with no matching position (to investigate) · 6 with an unknown outcome.

05:53– 06:40
Trip sto:63294804Insufficient coverage or identity; outcome unknown
06:00– 06:45
Trip sto:63296198Insufficient coverage or identity; outcome unknown
06:50– 07:41
Trip sto:63295042Insufficient coverage or identity; outcome unknown
07:00– 07:49
Trip sto:63296200Insufficient coverage or identity; outcome unknown
07:55– 08:49
Trip sto:63294583Insufficient coverage or identity; outcome unknown
08:03– 08:51
Trip sto:63296199Insufficient coverage or identity; outcome unknown
08:53– 09:43
Trip sto:63296167Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:56 a.m. EST; not actual start or end times.
09:00– 09:48
Trip sto:63294608Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 10:07 a.m. EST; not actual start or end times.
09:53– 10:42
Trip sto:63295911Vehicle position matchedFirst / last feed position: 9:51 a.m. EST / 10:51 a.m. EST; not actual start or end times.
10:01– 10:50
Trip sto:63295255Vehicle position matchedFirst / last feed position: 10:01 a.m. EST / 10:51 a.m. EST; not actual start or end times.
10:54– 11:43
Trip sto:63294609Vehicle position matchedFirst / last feed position: 10:52 a.m. EST / 11:56 a.m. EST; not actual start or end times.
11:00– 11:49
Trip sto:63295174Vehicle position matchedFirst / last feed position: 10:52 a.m. EST / 11:52 a.m. EST; not actual start or end times.

· Open all evidence for this day