← All agencies

Feed status · checked 2026-10-15

Réseau de transport de la Capitale (RTC)

Based on the official feed source on file

Service mode Bus

71.5 / 100

unchanged since 2026-10-14

Cataloged in Quebec, Canada.

Covers 64 daysAccessibility gapsRealtime not yet published

Source feed: https://cdn.rtcquebec.ca/Site_Internet/DonneesOuvertes/googletransit.zip Version history on the Mobility Database

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.

Checked for changes 6 hours ago; last changed 24 hours ago.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Réseau de transport de la Capitale (RTC)’s published feed lists 187 bus routes, 73,414 scheduled trips and 4,315 stops. Its service dates run from 2026-10-13 through 2026-12-18. The published file last changed on 2026-10-15.

Top things to fix

Fix 01

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 02

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

2523 of 4315 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

Fixing this covers 2,523 of 4,315 stops, about 58% of them.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +15 points in its category

Fix 03

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

46031 of 73414 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers 46,031 of 73,414 trips, about 63% of them.

⏱ A default or per-trip field in your export.worth about +9 points in its category

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • No need reading for this feed was on hand when this was built, so transit need is not known.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Fix 01 · Read the fix guide for scorecard_no_fare_data

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 64 days.
Published accessibility data
Accessibility information is stated for 41.5% of stops and 37.3% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness68.0 / 100

The MobilityData validator flagged 6 kinds of issue across 1140 instances (0 error, 1140 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 64 days.

Rider experience53.5 / 100

42% of stops state wheelchair accessibility (42% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility39.9 / 100

42% of stops state accessibility (42% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 1489 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Champlain/1005", "Champlain/1006", "Champlain/1007", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 4315 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1 (teal)
  • 11 (teal)
  • 12 (teal)
  • 13 (teal)
  • 136 (teal)
  • 13D (teal)
  • 16 (teal)
  • 18 (teal)
  • 185 (teal)
  • 19 (teal)
  • 22 (teal)
  • 231 (red)
  • 236 (red)
  • 237 (red)
  • 238 (red)
  • 250 (red)
  • 251 (red)
  • 253 (red)
  • 254 (red)
  • 255 (red)
  • 257 (red)
  • 258 (red)
  • 270 (red)
  • 272 (red)
  • 273 (red)
  • 274 (red)
  • 279 (red)
  • 28 (teal)
  • 280 (red)
  • 281 (red)
  • 282 (red)
  • 283 (red)
  • 284 (red)
  • 289 (red)
  • 29 (teal)
  • 290 (red)
  • 291 (red)
  • 292 (red)
  • 294 (red)
  • 3 (teal)
  • 31 (teal)
  • 32 (teal)
  • 330 (red)
  • 331 (red)
  • 336 (red)
  • 337 (red)
  • 338 (red)
  • 34 (teal)
  • 350 (red)
  • 354 (red)
  • 355 (red)
  • 358 (red)
  • 36 (teal)
  • 370 (red)
  • 372 (red)
  • 374 (red)
  • 380 (red)
  • 381 (red)
  • 382 (red)
  • 384 (red)
  • 39 (teal)
  • 3A (teal)
  • 4 (teal)
  • 405 (teal)
  • 430 (teal)
  • 450 (teal)
  • 5 (teal)
  • 51 (teal)
  • 52 (teal)
  • 53 (teal)
  • 530 (red)
  • 531 (red)
  • 536 (red)
  • 537 (red)
  • 538 (red)
  • 54 (teal)
  • 54G (teal)
  • 55 (teal)
  • 550 (red)
  • 554 (red)
  • 555 (red)
  • 558 (red)
  • 55G (teal)
  • 56 (teal)
  • 57 (teal)
  • 570 (red)
  • 572 (red)
  • 574 (red)
  • 58 (teal)
  • 580 (red)
  • 581 (red)
  • 582 (red)
  • 584 (red)
  • 59 (teal)
  • 6 (teal)
  • 61 (teal)
  • 630 (red)
  • 650 (red)
  • 690 (red)
  • 70 (teal)
  • 71 (teal)
  • 72 (teal)
  • 74 (teal)
  • 76 (teal)
  • 79 (teal)
  • 79B (teal)
  • 80 (teal)
  • 800 (yellow)
  • 801 (yellow)
  • 802 (yellow)
  • 803 (yellow)
  • 804 (yellow)
  • 805 (yellow)
  • 807 (yellow)
  • 80G (teal)
  • 81 (teal)
  • 82 (teal)
  • 82A (teal)
  • 82D (teal)
  • 82M (teal)
  • 84 (teal)
  • 84G (teal)
  • 85 (teal)
  • 86 (teal)
  • 88 (teal)
  • 9 (teal)
  • 90 (teal)
  • 904 (black)
  • 907 (black)
  • 90G (teal)
  • 91 (teal)
  • 92 (teal)
  • 925 (black)
  • 93 (teal)
  • 931 (black)
  • 936 (black)
  • 94 (teal)
  • 950 (black)
  • 954 (black)
  • 96 (teal)
  • 972 (black)
  • 980 (black)
  • 982 (black)
  • 984 (black)
  • 991 (black)
  • 992 (black)
Routes in Réseau de transport de la Capitale (RTC)'s feed
RouteTypeLine color
1Busteal
11Busteal
11GBusteal (no shape in feed)
12Busteal
13Busteal
133Busteal (no shape in feed)
136Busteal
13ABusteal (no shape in feed)
13BBusteal (no shape in feed)
13DBusteal
14Busteal (no shape in feed)
14ABusteal (no shape in feed)
14GBusteal (no shape in feed)
15Busteal (no shape in feed)
15ABusteal (no shape in feed)
15BBusteal (no shape in feed)
16Busteal
18Busteal
185Busteal
19Busteal
214Busred (no shape in feed)
215Busred (no shape in feed)
22Busteal
230Busred (no shape in feed)
231Busred
236Busred
237Busred
238Busred
239Busred (no shape in feed)
25Busteal (no shape in feed)
250Busred
251Busred
253Busred
254Busred
255Busred
257Busred
258Busred
25GBusteal (no shape in feed)
270Busred
272Busred
273Busred
274Busred
277Busred (no shape in feed)
279Busred
28Busteal
280Busred
281Busred
282Busred
283Busred
284Busred
289Busred
29Busteal
290Busred
291Busred
292Busred
294Busred
3Busteal
31Busteal
315Busred (no shape in feed)
32Busteal
33Busteal (no shape in feed)
330Busred
331Busred
332Busred (no shape in feed)
336Busred
337Busred
338Busred
34Busteal
344Busred (no shape in feed)
350Busred
354Busred
355Busred
358Busred
36Busteal
370Busred
372Busred
374Busred
377Busred (no shape in feed)
380Busred
381Busred
382Busred
384Busred
39Busteal
391Busred (no shape in feed)
3ABusteal
4Busteal
400Busteal (no shape in feed)
402Busteal (no shape in feed)
405Busteal
410Busteal (no shape in feed)
420Busteal (no shape in feed)
430Busteal
450Busteal
460Buswhite (no shape in feed)
5Busteal
51Busteal
52Busteal
53Busteal
530Busred
531Busred
536Busred
537Busred
538Busred
54Busteal
54ABusteal (no shape in feed)
54GBusteal
55Busteal
550Busred
554Busred
555Busred
558Busred
55ABusteal (no shape in feed)
55GBusteal
56Busteal
57Busteal
570Busred
572Busred
574Busred
577Busred (no shape in feed)
58Busteal
580Busred
581Busred
582Busred
584Busred
59Busteal
6Busteal
61Busteal
630Busred
64Busteal (no shape in feed)
65Busteal (no shape in feed)
650Busred
690Busred
70Busteal
71Busteal
72Busteal
74Busteal
75Busteal (no shape in feed)
76Busteal
77Busteal (no shape in feed)
79Busteal
79BBusteal
79GBusteal (no shape in feed)
80Busteal
800Busyellow
801Busyellow
802Busyellow
803Busyellow
804Busyellow
805Busyellow
807Busyellow
80ABusteal (no shape in feed)
80GBusteal
81Busteal
82Busteal
82ABusteal
82DBusteal
82MBusteal
84Busteal
84GBusteal
85Busteal
86Busteal
86GBusteal (no shape in feed)
88Busteal
9Busteal
90Busteal
904Busblack
907Busblack
90GBusteal
91Busteal
915Busblack (no shape in feed)
92Busteal
925Busblack
92ABusteal (no shape in feed)
93Busteal
931Busblack
936Busblack
94Busteal
950Busblack
954Busblack
96Busteal
972Busblack
980Busblack
982Busblack
984Busblack
991Busblack
992Busblack
999Buswhite (no shape in feed)
List every stop
  • Champlain/1005
  • Champlain/1006
  • Champlain/1007
  • Champlain/1008
  • Champlain/1009
  • Champlain/1010
  • T. D'Youville
  • La Croix-Rouge
  • Champlain/1013
  • Champlain/1014
  • Petit-Champlain
  • Trav. Qc-Lévis
  • M. Civilisation
  • St-Pierre
  • Espace 400
  • St-Thomas
  • Gare-Palais/1022
  • J.-Lesage
  • St-Dominique
  • du Pont
  • R.-Lévesque
  • de la Couronne
  • Dorchester
  • Caron
  • Langelier
  • Laviolette
  • des Oblats/1038
  • de Carillon
  • Renaud
  • Bigaouette
  • du Sacré-Coeur
  • Montmagny
  • St-Bernard
  • R.-Jobin
  • E.-Lamontagne
  • Kirouac
  • Pente-Douce
  • Ste-Foy/1051
  • Thornhill
  • du Parc-Champoux
  • Sheppard
  • St-Paul
  • du Ch.-Morel
  • St-Paul
  • J.-Rousseau
  • Preston
  • William
  • du Ch.-Morel
  • Sarah
  • du Parc-Champoux
  • J.-Lemoine
  • Thornhill
  • du Ravin
  • Grande Allée
  • Belvédère
  • H. St-Sacrement
  • Ste-Foy
  • R.-Jobin
  • St-Bernard
  • Langelier
  • Caron
  • Dorchester
  • de la Couronne
  • du Pont
  • St-Dominique
  • J.-Lesage
  • Gare-Palais/1108
  • St-Thomas
  • Espace 400
  • St-Pierre
  • du Card.-M-Roy
  • M. Civilisation
  • Trav. Qc-Lévis
  • Petit-Champlain
  • Champlain/1116
  • Champlain/1117
  • des Sapeurs
  • Champlain/1119
  • Champlain/1120
  • Champlain/1121
  • Champlain/1122
  • D'Auteuil/1124
  • Non commercial
  • Non commercial
  • Pr.-Édouard/1125
  • Nérée-Tremblay
  • Bourg-Royal/1126
  • de l'Amiral
  • de la Montagne
  • du Sault
  • 5e Rue
  • Deblois
  • de Bellevue
  • de la Canoterie
  • du Golf
  • du Golf
  • du Golf
  • H. Hôtel-Dieu
  • du Golf
  • de la Faune
  • 7e Rue
  • de Vénus
  • Brousseau
  • de Saint-Julien
  • 48e Rue
  • St-Jean/1133
  • De Salaberry
  • De Salaberry
  • Hôtel de ville
  • Poulin
  • des Prairies
  • Univ. du Québec
  • Palais Montcalm
  • de la Durance
  • H. Hôtel-Dieu
  • De Lestres
  • 9e Rue
  • Saint-Michel
  • Lorquet
  • de la Canoterie
  • G.-Lalemant
  • MacKay
  • Jacques-Bédard
  • D'Entremont
  • D'Entremont
  • du L.-St-Charles
  • Langelier
  • de la Reine
  • St-Joseph
  • M.-Incarnation
  • Lebouthillier
  • Ste-Foy
  • des Brumes
  • des Branches
  • des Arbrisseaux
  • des Alluvions
  • St-Vallier/1170
  • Panet
  • Lebouthillier
  • de Verdun
  • St-Joseph/1184
  • des Commissaires
  • St-Anselme
  • R.-Lévesque
  • D'Youville
  • Collège Bart
  • Bonne-Entente
  • Place-J.-Cartier
  • des Embarcations
  • St-Omer
  • 4e Rue
  • 9e Rue
  • St-Léandre
  • Masson/1210
  • H. St-François
  • 18e Rue
  • 24e Rue
  • Peupliers/1218
  • 1re Avenue/1221
  • des Cerisiers
  • du Colisée/1223
  • Duval/1224
  • St-Léandre
  • V.-Martin
  • Sarrazin
  • la Concorde/1229
  • Peupliers/1230
  • des Saules/1231
  • la Concorde/1232
  • Dumas
  • Duval/1234
  • du Colisée/1235
  • Peupliers/1239
  • 24e Rue
  • 18e Rue
  • des Gerbes
  • H. St-François
  • de la Griotte
  • 9e Rue
  • 4e Rue
  • St-Omer
  • Croix-Rouge/1254
  • Poulin
  • La Croix-Rouge
  • T. Parc-Victoria
  • Pr.-Édouard/1260
  • Place J.-Cartier
  • De Ste-Hélène
  • Lortie
  • Collège Bart
  • Bonne-Entente
  • St-Louis
  • Stade Canac
  • R.-Rumilly
  • Daniel
  • François-1er
  • De L'Espinay
  • De La Martinière
  • De Meulles
  • E.-Lamontagne
  • J.-Mance
  • 1re Avenue
  • Benoît-XV
  • 4e Avenue
  • 8e Avenue
  • la M.-Clarisse
  • H. Enfant-Jésus
  • Alexandra/1305
  • Poncelet
  • 11e Rue
  • M.-Gosselin/1308
  • Bardy
  • des Intendants
  • 25e Rue/1311
  • 24e Rue/1312
  • Baldwin
  • Grandville/1315
  • de la Canardière
  • H. Enfant-Jésus
  • la Capricieuse
  • 8e Avenue
  • 4e Avenue/1322
  • Benoît-XV
  • 1re Avenue
  • J.-Mance
  • De Meulles
  • De La Martinière
  • De L'Espinay
  • Pte-Lièvres/1332
  • Laurentienne
  • Cardinal-Roy
  • Stade Canac
  • 3e Avenue/1336
  • 1re Avenue
  • 3e Avenue/1339
  • 5e Rue
  • Canardière/1346
  • St-Jean/1349
  • Morand/1350
  • I.-LeVasseur
  • Fortier/1354
  • J.-Parent/1355
  • Sicotte
  • D'Estimauville
  • Ste-Anne/1359
  • T. Beauport
  • Ste-Anne
  • Becquet/1365
  • Becquet/1366
  • Bazire
  • and 4065 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 14 checks — unchanged since 2026-10-14.

2026-10-02: 71.52026-10-03: 71.52026-10-04: 69.82026-10-05: 71.52026-10-06: 73.22026-10-07: 73.22026-10-08: 71.52026-10-09: 71.52026-10-10: 71.52026-10-11: 71.52026-10-12: 69.72026-10-13: 71.52026-10-14: 71.52026-10-15: 71.5
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-10-0271.5 first check
2026-10-0371.5 no change
2026-10-0469.8 down 1.7
2026-10-0571.5 up 1.7
2026-10-0673.2 up 1.7
2026-10-0773.2 no change
2026-10-0871.5 down 1.7
2026-10-0971.5 no change
2026-10-1071.5 no change
2026-10-1171.5 no change
2026-10-1269.7 down 1.8
2026-10-1371.5 up 1.8
2026-10-1471.5 no change
2026-10-1571.5 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-10-151dcd5fd1bc772026-12-18Current rubric: see the trend above
2026-10-13 to 2026-10-14 (2 checks)2a97408b14562026-12-18Current rubric: see the trend above
2026-10-12c9e18d236ab72026-12-18Current rubric: see the trend above
2026-10-10 to 2026-10-11 (2 checks)e863142513f32026-12-18Current rubric: see the trend above
2026-10-0930ac33ec13d22026-12-18Current rubric: see the trend above
2026-10-08751fca66d0cd2026-12-18Current rubric: see the trend above
2026-10-06 to 2026-10-07 (2 checks)5e38967a505a2026-12-18Current rubric: see the trend above
2026-10-052d015e41b1112026-12-18Current rubric: see the trend above
2026-10-048290423267d12026-12-18Current rubric: see the trend above
2026-10-03a2dec5d9a5742026-12-18Current rubric: see the trend above
2026-10-0219752f1a93502026-12-18Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)5cf0a3181ed72026-12-18C, 71.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

Showing the 12 most recent of 66 periods.

What changed over time

On 2026-10-02 this feed started at grade C. On 2026-10-04 the grade moved from C to D. On 2026-10-05 the grade moved from D to C. On 2026-10-12 the grade moved from C to D. As of 2026-10-15 it holds grade C.

A plain-language history of this feed, newest first.

  • 2026-10-13 Grade went D to C, correctness rose 4 points.
  • 2026-10-12 Grade went C to D, correctness fell 4 points.
  • 2026-10-05 Grade went D to C, correctness rose 4 points.
  • 2026-10-04 Grade went C to D, correctness fell 4 points.

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Warning46031 instances

    46031 of 73414 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning2523 instances

    2523 of 4315 stops don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning897 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning237 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 instances

    Same name and description for stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 42% of stops and 37% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 64 days.
Accessible Not yet
States wheelchair access on 42% of stops and 37% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 237 of 4315 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 63 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 68 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 100 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 54 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Canada portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Quebec

Other scorecards in Quebec, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Réseau de transport de la Capitale (RTC): GTFS feed quality grade C, 71.5 of 100, checked 2026-10-15. GTFS Scorecard.

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/rtc-quebec/2026-10-15.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-10-15. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.