Feed status · checked 2026-07-19
BC Transit (Nanaimo Regional Transit System)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in British Columbia, Canada.
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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
840 of 840 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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
1553 of 1553 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
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. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
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. Self-check a feed before you publish.
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. · Read the fix guide
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. Self-check a feed before you publish.
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 48 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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
The MobilityData validator flagged 6 kinds of issue across 172 instances (0 error, 134 warning, 38 informational).
Service data covers the next 48 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (5, 7, 8, 25, 30, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
797 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Park Ave at 6th St", "Park Ave at Honey Dr", "Park Ave at 7th St", 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (purple)
- 15 (red)
- 15A (red)
- 20 (teal)
- 20A (teal)
- 25 (yellow)
- 30 (orange)
- 31 (brown)
- 40 (teal)
- 5 (gray)
- 6 (teal)
- 7 (pink)
- 70 (gray)
- 72 (yellow)
- 78 (brown)
- 8 (green)
- 88 (gray)
- 9 (brown)
- 97 (teal)
- 98 (purple)
- 99 (gray)
| Route | Type | Line color |
|---|---|---|
| 1 Nanaimo Rapid Line | Bus | purple |
| 15 VIU Connector via Parkway | Bus | red |
| 15A VIU Connector via Jingle Pot | Bus | red |
| 20 Hammond Bay | Bus | teal |
| 20A Hammond Bay via Dover | Bus | teal |
| 25 Ferry Shuttle | Bus | yellow |
| 30 NRGH | Bus | orange |
| 31 Lantzville | Bus | brown |
| 40 VIU Express | Bus | teal |
| 5 Fairview | Bus | gray |
| 6 Harewood | Bus | teal |
| 7 Cinnabar | Bus | pink |
| 70 NCX Nanaimo - Cowichan Express | Bus | gray |
| 72 Downtown/Country Club | Bus | yellow |
| 78 Cassidy/Airport | Bus | brown |
| 8 Cedar | Bus | green |
| 88 Parksville | Bus | gray |
| 9 Intercity | Bus | brown |
| 97 Eaglecrest | Bus | teal |
| 98 Qualicum Beach | Bus | purple |
| 99 Deep Bay | Bus | gray |
This feed has 840 stops.
List every stop
- Jingle Pot Rd at Ashlee Rd
- Fern Rd W at Beach Rd
- Fern Rd W at Memorial Ave
- Fern Rd E at Berwick Rd S
- Berwick Rd S at 6th Ave E
- Rupert Rd E at Berwick Rd S
- Rupert Rd E at Qualicum Rd
- Village Green Mall
- Mostar Rd at Jordan Ave
- Stanhope Rd at Parkside Cres
- Stanhope Rd at Parkside Cres W
- Stanhope Rd at Belson St
- Stanhope Rd at Parkside Cres E
- Pym St N at Sanderson Rd
- Pym St N at Sanderson Rd
- Pym St N at Temple St
- Pym St N at Temple St
- McMillan St at Harrison Ave
- Island Hwy E at Tuan Rd
- Island Hwy E at Resort Way
- Barons Rd at Departure Bay Rd
- Leon Rd at Horne Lake Rd
- Island Hwy W at Lee Rd E
- Island Hwy W at Lee Rd W
- Island Hwy E at Riverside Rd
- Island Hwy E at Riverside Rd
- Island Hwy W at Lions Way
- Island Hwy W at Magnolia Court
- Thompson Clark Dr E at Henry Morgan Dr
- Deep Bay Marina
- Wembley Rd at Roberton Blvd
- Island Hwy W at Wembley Centre
- Island Hwy W at Wembley Centre
- Rupert Rd E at Hollywood Rd
- Rupert Rd E at Bluebird Pl
- Rupert Rd E at Ravensbourne Lane
- Miraloma Dr at Chartwest Crt
- Chartwell Blvd at Miraloma Dr
- Ormonde Rd at Devon Pl
- Ormonde Rd at Yambury Rd
- Ormonde Rd at Boultbee Dr
- Boultbee Dr at Bunker Pl
- Island Hwy W at Columbia Dr
- Johnstone Rd at Sumar Lane
- Pintail Dr at Johnstone Rd
- Pintail Dr at Point Mercer Dr
- Pintail Dr at Yambury Rd
- Pintail Dr at Eaglecrest Dr
- Eaglecrest Dr at Mallard Pl
- Harlequin Rd at Eaglecrest Dr
- Royal Dornoch Dr at Fairways Dr
- Royal Dornoch Dr at Troon Close
- Country Club Dr at Fairways Dr
- Hwy 19A at Milner Gardens
- Hwy 19A at Qualicum Rd
- Hwy 19A at Hall Rd
- Hemsworth Rd at Quatsino Rd
- Hemsworth Rd at Dogwood Rd
- Dogwood Rd at Qualicum Rd
- Qualicum Rd at Chester Rd
- Jones St at Rupert Rd W
- Arbutus St at McRae Pl
- 800 Blk Chestnut St
- Arbutus St at Birch Ave
- Arbutus St at 1st Ave W
- Arbutus St at Hoylake Rd W
- Crescent Rd W at Arbutus St
- Crescent Rd W at Alder St
- Garrett Rd Turnaround
- Crescent Rd W at Beach Rd
- Crescent Rd W at Memorial Ave
- Island Hwy W at Memorial Ave
- 2800 Blk Island Hwy W
- Island Hwy W at Bay St
- 3100 Blk Island Hwy W
- Island Hwy W at Crescent Rd W
- Island Hwy W at Beach Terr
- Garrett Rd at Park Ridge Pl
- Crescent Rd W at Rye Rd
- Canyon Crescent Rd at Garrett Rd
- Canyon Crescent Rd at Hoylake Rd W
- Mill Rd at Arbutus St
- Mill Rd at Alder St
- Mill Rd at Rye Rd
- Mill Rd at Beach Rd
- Beach Rd at 1st Ave W
- Fern Rd W at Beach Rd
- Arbutus St at Hoylake Rd W
- Berwick Rd S at Garden Rd E
- Island Hwy E at Rath Rd
- Island Hwy E at Huntley Rd
- Island Hwy W at Fisheries Rd
- Salish Way at River Rd
- Island Hwy W at Lions Way
- Island Hwy W at Magnolia Court
- Island Hwy W at Fisheries Rd
- Leon Rd at Berkshire Rd
- Oceanside Health Centre
- Church Rd at Wembley Rd
- Island Hwy E at Morello Rd
- 900 Blk Berwick Rd S
- Jingle Pot Rd at Black Diamond Dr
- Northwest Bay Rd at Island Hwy E
- Emerald Dr at Uplands Dr
- Sunrise Dr at Island Hwy W
- Bay A at Downtown Nanaimo Exch
- Bay B at Downtown Nanaimo Exch
- Bay C at Downtown Nanaimo Exch
- Bay D at Downtown Nanaimo Exch
- Bay E at Downtown Nanaimo Exch
- Bay F at Downtown Nanaimo Exch
- Bay G at Downtown Nanaimo Exch
- 4th St at Hillcrest Ave
- 4th St at Wakesiah Ave
- Bruce Ave at Mulberry Dr
- Bruce Ave at Mulberry Dr
- 400 Blk 10th St
- 10th St at Park Ave
- 10th St at Douglas Ave
- 10th St at Douglas Ave
- 10th St at Southside Dr
- 10th St at Southside Dr
- Schoolhouse Rd at Morden Rd
- S Wellington Rd at Morden Rd
- Front St at Museum Way
- Vowels Rd at Angus Rd
- Hallberg Rd at Carden Rd
- Hallberg Rd at Seabird Rd
- Hallberg Rd at Pelter Pl
- Timberlands Rd at Timberlands Park
- Timberlands Rd at Hwy 1
- Nanaimo Airport
- Lawlor Rd at 11th St
- Island Hwy at Rutherford Rd
- Island Hwy at Mostar Rd
- Schoolhouse Rd at Fielding Rd
- Bruce Ave at 8th St
- Bruce Ave at 8th St
- Fitzwilliam St at Prideaux St
- Bowen Rd at Northfield Rd
- Albert St at Selby St
- Powder Works Rd at Boxwood Rd
- Powder Works Rd at Boxwood Rd
- Boxwood Rd at Northfield Rd
- Boxwood Rd at Northfield Rd
- Lantzville Rd at Snaw-Naw-As Rd
- Dickinson Rd at Dover Rd
- Norwell Dr at 105th St
- 7900 Blk Lantzville Rd
- Lantzville Rd at Benwaldun Rd
- Northfield Rd at Bowen Rd
- Northfield Rd at Sarnia Rd
- Oyster Sto'Lo Rd at Hwy 1
- Meredith Rd at Boxwood Rd
- Meredith Rd at Boxwood Rd
- Meredith Rd at Tulsa Rd
- Meredith Rd at Tulsa Rd
- Despard Ave W at Hackberry Pl
- Despard Ave W at Hackberry Pl
- Comox Rd at Cliff St
- Wakesiah Ave at Foster St
- Nanaimo Port Authority
- Wakesiah Ave at Foster St
- Wakesiah Ave at 4th St
- Jingle Pot Rd at Black Diamond Dr E
- Metral Dr at Dunbar Rd
- Albert St at Milton St
- Beverly St at Duncan St
- Canada Ave at Station St
- Canada Ave at Beverly St
- 1st Ave at Hwy 1
- Drinkwater Rd at Cowichan Commons
- Jingle Pot Rd at Sarum Rise Way
- Jingle Pot Rd at Bird Sanctuary Dr
- Jingle Pot Rd at Valley Oak Dr
- Jingle Pot Rd at Calder Rd
- Westwood Rd at Rockwood Pl
- Arbot Rd at Westwood Rd
- Arbot Rd at Fountain Gate Pl
- Arbot Rd at South View Rd
- Mill Rd at Westberry Pl
- Ashlee Rd at Mill Rd
- Ashlee Rd at Towerview Cres
- Ashlee Rd at Holland Rd
- Jingle Pot Rd at Ashlee Rd
- Jingle Pot Rd at Calder Rd
- Jingle Pot Rd at Black Diamond Dr W
- Jingle Pot Rd at Bird Sanctuary Dr
- Jingle Pot Rd at Derby Pl
- Wakesiah Ave at Taylor Pl
- Wakesiah Ave at Foster St
- Fitzwilliam St at Wesley St
- Wallace St at Fitzwilliam St
- Victoria Cres at Albert St
- Front St at Museum Way
- Front St at Church St
- Comox Rd at Terminal Ave N
- Stewart Ave at Dawes St
- Stewart Ave at Mt Benson St
- Townsite Rd at Terminal Ave N
- Townsite Rd at Churchill Ave
- Townsite Rd at Millstone Ave
- Millstone Ave at Hunter St
- Millstone Ave at Cadogan St
- Princess Royal Ave at Hemlock St
- Estevan Rd at Brierley Hill
- Estevan Rd at Maple St
- Estevan Rd at Brechin Rd
- Departure Bay Rd at Estevan Rd
- Marlborough Dr at Lynburn Cres
- Glenayr Dr at Marlborough Dr
- Glenayr Dr at Argyle Ave
- Glenayr Dr at Lynburn Cres
- Glenayr Dr at Wingrove St
- Bay St at Haliday Cres
- Bay St at Newton St
- Neyland Rd at Crestwood Pl
- Neyland Rd at Departure Bay Rd
- Departure Bay Rd at Shamrock Pl
- Departure Bay Rd at Rock City Rd
- Departure Bay Rd at Mexicana Rd
- Bay H at Country Club Exch
- 3100 Blk Barons Rd
- Uplands Dr at Stonewood Pl
- Uplands Dr at Butternut Dr
- Uplands Dr at Rutherford Rd
- Uplands Dr at Primrose Dr
- Uplands Dr at Edgewater Lane
- Uplands Dr at Turner Rd
- Uplands Dr at Parkwood Dr
- Uplands Dr at Hammond Bay Rd
- Uplands Dr at Ocean Walk Dr
- Uplands Dr at McRobb Ave
- Dover Rd at Blueback Rd
- Dover Rd at Lewis Rd
- Dover Rd at Harrier Rd
- Mary Ellen Dr at Dover Rd
- Dover Rd at Mary Ellen Dr
- Dover Rd at Dickinson Rd
- Dover Rd at Lewis Rd
- Dover Rd at Applecross Rd
- Uplands Dr at McRobb Ave
- Uplands Dr at Ocean Walk Dr
- Uplands Dr at Hammond Bay Rd
- Uplands Dr at Parkwood Dr
- Uplands Dr at Turner Rd
- Uplands Dr at Edgewater Lane
- Uplands Dr at Primrose Dr
- Uplands Dr at Rutherford Rd
- Uplands Dr at Butternut Dr
- and 590 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning1553 instances
1553 of 1553 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning840 instances
840 of 840 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning109 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.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning21 instances
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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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.)
Validator rule: stop_without_stop_time · Read the fix guide · 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.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info38 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 48 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% 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.
- 2 of 840 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 48 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 73 / 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 80 / 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 38 / 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.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this 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/bc-transit-nanaimo/2026-07-19.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-07-19. 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.