Feed status · checked 2026-09-05
Bilbobus
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Bizkaia, Spain.
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.3, validator 8.0.1.
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.
Top things to fix
Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid row length (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
Check the flagged trips in your scheduling software; remove them or restore their missing stops.Likely your export tool
Some trips serve fewer than two stops. A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
⏱ Worth a vendor question if it appears often.worth about +8 points in its category
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.
- Feed evidence
- Invalid row length (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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
- Feed evidence
- Some trips serve fewer than two stops.
- Next action
- Check the flagged trips in your scheduling software; remove them or restore their missing stops.
- 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.
Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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.
Check the flagged trips in your scheduling software; remove them or restore their missing stops.
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 298 days.
- Published accessibility data
- Accessibility information is stated for 99.8% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 7 kinds of issue across 1011 instances (1 error, 1006 warning, 4 informational).
Service data covers the next 298 days.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
122 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("IGNACIO ELLACURÍA / ELORRIETA", "DON BOSCO / UGARTEKO", "UGARTEKO / IBARREKOLANDA", 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.
Fares are applied to trips.
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 532 stops.
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.
- 18 (green)
- 22 (green)
- A9 (green)
- 27 (green)
- 55 (green)
- 30 (green)
- 34 (green)
- 38 (green)
- 40 (green)
- 43 (green)
- 48 (green)
- 56 (green)
- 50 (green)
- 57 (green)
- 58 (green)
- 62 (green)
- 71 (green)
- 72 (green)
- 75 (green)
- 77 (green)
- 76 (green)
- 85 (green)
- 88 (green)
- A1 (green)
- A2 (green)
- A3 (green)
- A4 (green)
- A5 (green)
- A6 (green)
- G1 (green)
- G2 (green)
- G3 (green)
- G4 (green)
- G5 (green)
- G6 (green)
- G7 (green)
- G8 (green)
- 03 (green)
- 01 (green)
- A8 (green)
- 28 (green)
- A7 (green)
- 10 (green)
- 11 (green)
- 13 (green)
- BT (green)
| Route | Type | Line color |
|---|---|---|
| 18 SAN IGNACIO - ZORROTZA | Bus | green |
| E3 PLAZA CIRCULAR-FRONTON BIZKAIA-BILBAO ARENA | Bus | green (no shape in feed) |
| 22 SARRIKUE - ATXURI | Bus | green |
| A9 HOSPITAL SANTA MARINA - ABANDO | Bus | green |
| E28 URIBARRI - ALTAMIRA | Bus | green (no shape in feed) |
| E38 OTXARKOAGA / INTERMODAL | Bus | green (no shape in feed) |
| E56 LA PEÑA - SAGRADO CORAZÓN | Bus | green (no shape in feed) |
| E57 MIRIBILLA - HOSPITAL BASURTO | Bus | green (no shape in feed) |
| E62 SAGRADO CORAZÓN - ARABELLA | Bus | green (no shape in feed) |
| 27 ARABELLA - BETOLATZA | Bus | green |
| 55 MINA DEL MORRO - MIRIBILLA | Bus | green |
| 30 TXURDINAGA - MIRIBILLA | Bus | green |
| EA4 UNIVERSIDAD - DEUSTU | Bus | green (no shape in feed) |
| 34 OTXARKOAGA - SANTUTXU | Bus | green |
| 38 OTXARKOAGA - INTERMODAL | Bus | green |
| 40 LA PEÑA - PLAZA CIRCULAR | Bus | green |
| 43 GARAIZAR - SANTUTXU | Bus | green |
| 48 SANTUTXU - LEZEAGA | Bus | green |
| 56 LA PEÑA - SAGRADO CORAZÓN | Bus | green |
| 50 BUIA - LA PEÑA | Bus | green |
| 57 MIRIBILLA - HOSPITAL BASURTO | Bus | green |
| 58 MONTE CARAMELO - ATXURI | Bus | green |
| 62 SAGRADO CORAZÓN - ARABELLA | Bus | green |
| 71 MIRIBILLA - SAN IGNACIO | Bus | green |
| 72 LARRASKITU - CASTAÑOS | Bus | green |
| 75 SAN ADRIAN - ATXURI | Bus | green |
| 77 PEÑASCAL - MINA DEL MORRO | Bus | green |
| 76 ARTAZU/XALBADOR - PLAZA ELÍPTICA | Bus | green |
| 85 ZAZPILANDA - ATXURI | Bus | green |
| 88 KASTREXANA - INDAUTXU | Bus | green |
| A1 ASUNCION - PLAZA CIRCULAR | Bus | green |
| A2 SOLOKOETXE - PLAZA CIRCULAR | Bus | green |
| A3 OLABEAGA - PLAZA ELÍPTICA | Bus | green |
| A4 ZORROTZAURRE - DEUSTU | Bus | green |
| A5 PRIM - PLAZA CIRCULAR | Bus | green |
| A6 ARANGOITI - DEUSTU | Bus | green |
| G1 ARABELLA - PLAZA CIRCULAR | Bus | green |
| G2 OTXARKOAGA - PLAZA CIRCULAR | Bus | green |
| G3 LARRASKITU - PLAZA CIRCULAR | Bus | green |
| G4 LA PEÑA - PLAZA CIRCULAR | Bus | green |
| G5 MIRIBILLA - PLAZA CIRCULAR | Bus | green |
| G6 ZORROTZA - PLAZA CIRCULAR | Bus | green |
| G7 MINA DEL MORRO - PLAZA CIRCULAR | Bus | green |
| G8 ARANGOITI - PLAZA CIRCULAR | Bus | green |
| 03 PLAZA CIRCULAR - OTXARKOAGA | Bus | green |
| 01 ARANGOITI - PLAZA CIRCULAR | Bus | green |
| A8 SAN JUSTO - AMETZOLA | Bus | green |
| 28 URIBARRI - ALTAMIRA | Bus | green |
| A7 ARTXANDA - ARENAL | Bus | green |
| 10 ELORRIETA - PLAZA CIRCULAR | Bus | green |
| E2 PLAZA CIRCULAR - FRONTON BIZKAIA | Bus | green (no shape in feed) |
| E5 PLAZA FUNICULAR - ARTXANDA | Bus | green (no shape in feed) |
| E7 ABANDO - BILBAO ARENA | Bus | green (no shape in feed) |
| 11 DEUSTU - ATXURI | Bus | green |
| 13 SAN IGNACIO - TXURDINAGA | Bus | green |
| BT Bus Turístico | Bus | green |
List every stop
- CAMPO VOLANTÍN / LA SALVE
- LUIS BRIÑAS 27
- ARTXANDA / LA ESPERANZA
- ENEKURI / GASOLINERA
- BERRIZ / CAMPO DE TIRO
- ENEKURI
- ENEKURI / fte. SAN PABLO
- ARTXANDA / NOGARO
- ARTXANDA / FUNICULAR
- PINTOR LOSADA 26
- RIBERA DE DEUSTU 57
- TRISTÁN DE LEGUIZAMÓN 5
- RIBERA DE DEUSTU fte. 59
- UGARTE fte. 7
- URKIOLA 1
- ZORROTZAURRE 9
- ZORROTZAURRE fte. 9
- ZORROTZAURRE 17
- ZORROTZAURRE fte. 17
- LEHENDAKARI AGUIRRE 149
- LEHENDAKARI AGUIRRE 154
- LARRASKITUBIDEA fte. 81
- MATIKO 27
- FUNICULAR
- LEHENDAKARI AGUIRRE 161
- LEHENDAKARI AGUIRRE 179
- PLAZA LEVANTE
- ORIXE 54
- IGNACIO ELLACURÍA / ELORRIETA
- CAMINO MIRAMAR / ARANEKOBIDEA
- CAMINO MIRAMAR fte. 47
- MINA SAN LUIS
- ARANEKO / CEMENTERIO
- BERRIZBIDEA
- SABINO ARANA 32
- MORGAN / CLÍNICA IMQ (provisional)
- CAMINO MIRAMAR / ESCUELA
- ESKURTZE fte. 10
- CAMPO VOLANTÍN 23
- ARANEKO fte.22
- ARANEKO 17
- EGILEOR 4
- ATXETABIDEA / JESUITINAS
- GANEKOGORTA 10
- GORBEIA fte. 3
- URAZURRUTIA 29
- MONTE GANETA fte. 7
- SENDEJA fte. 5
- VIUDA DE EPALZA 1 / SAN NICOLÁS
- ARENAL / fte. SAN NICOLÁS
- PUENTE DEL ARENAL
- CAMPO VOLANTÍN fte. 21
- ARENAL / ARRIAGA
- SAN NICOLÁS 4
- MONTE ELORRIAGA
- UNAMUNO
- FIKA 2
- PRIM 22 Bis
- PRIM 36
- PRIM 52
- PRIM 60
- AMADEO DEPRIT 1
- ZORROTZA-KASTREXANA 10
- AVENIDA FERROCARRIL
- AMADEO DEPRIT / DOLARETXE
- JAÉN 7
- AMADEO DEPRIT / PEDRO CORTÉS
- AMADEO DEPRIT 8
- ITURRIBIDE 53
- FIKA 8
- FIKA 18
- MADARIAGA 13
- FIKA 22
- MASUSTEGI fte. 21
- MASUSTEGI 21
- ZABALBIDE 41
- JULIO URQUIJO
- MASUSTEGI 3
- CAMPO VOLANTÍN 13
- SANTUTXU 2
- ZABALBIDE fte. 32
- ZABALBIDE 7
- DIECISÉIS DE AGOSTO
- PLAZUELA SANTOS JUANES 7
- PLAZUELA SANTOS JUANES 4
- ATXURI 15
- ATXURI fte. 15
- ATXURI 49
- SAN MAMÉS
- HOSPITAL BASURTO
- GRAN VÍA 85
- ATXURI fte. 49
- INDALECIO PRIETO 1
- INDALECIO PRIETO fte. 12
- AMBULATORIO TXURDINAGA
- INDALECIO PRIETO 16
- ZUMALACARREGUI / fte. MAKUA
- MAKUA
- TXOMIN GARAT 4
- JESÚS GALÍNDEZ / TXOMIN GARAT
- JESÚS GALÍNDEZ 3
- TXOMIN GARAT 12
- AYUNTAMIENTO
- TXOMIN GARAT 9
- GABRIEL ARESTI / fte. AMBULATORIO
- TXOMIN GARAT 40
- ORNILLA / ARTALANDIO
- ARTALANDIO 3
- JESÚS GALÍNDEZ / ADORATRICES
- JESÚS GALÍNDEZ 26
- GARAIZAR / IKASTOLA
- ERNESTO ERKOREKA 8
- GARAIZAR fte. 16
- ORNILLA / PAU CASALS
- PAU CASALS / JESÚS GALÍNDEZ
- PAU CASALS 16
- ZIZERUENA / IGLESIA
- LARRATUNDU 21
- UGARTE 2
- ZIZERUENA 22
- CRISTO 1
- LANGARAN 44
- ARBOLANTXA 18
- TXOTENA 62
- TXOTENA 8
- TXOTENA / LANGARAN
- JULIÁN GAIARRE fte. 61
- JULIÁN GAIARRE 61
- JULIÁN GAIARRE fte. 39
- JULIÁN GAIARRE 39
- JULIÁN GAIARRE 82
- TIBOLI 12
- JULIÁN GAIARRE 33
- JULIÁN GAIARRE 23
- JULIÁN GAIARRE 36
- ONDARROA / PARQUE
- FERNANDO JIMÉNEZ 12
- JULIÁN GAIARRE fte. 6
- JULIÁN GAIARRE 10
- CIRCO AMATEUR / BOLUETA
- CIRCO AMATEUR / POLIDEPORTIVO
- CIRCO AMATEUR / fte. POLIDEPORTIVO
- MATIKO 1
- ORNILLA fte.12
- SANTA CLARA fte. 12
- ENRIQUE IBARRETA 2
- ITURRIAGA 58
- ANTONIO EGUILUZ 19
- SAGARMINAGA 32
- SANTUTXU fte.45
- RICARDO ARREGUI 33
- SANTUTXU 48
- SANTUTXU 18
- MERCADO DE LA RIBERA
- MUELLE DE LA MERCED 3
- CORTES fte. 2
- TIBOLI 1
- MAURICE RAVEL / MIRADOR
- OLANO fte.4
- URAZURRUTIA / SALA CUNA
- ANSELMA DE SALCES fte.2
- URAZURRUTIA 14
- URAZURRUTIA 40
- ZAMACOLA 4
- ZAMACOLA 26
- URAZURRUTIA
- ZAMACOLA 39
- ZAMACOLA 70
- ZAMACOLA fte. 84
- ZAMACOLA / ESCUELA
- ABUSU / IBAIZABAL
- ZAMACOLA 116
- ABUSU / IBAIALDE
- ZAMACOLA 150
- ABUSU / IBAIEDER
- ZAMACOLA 168
- BUIA / fte. BOLINTXUBIDEA
- BUIA / BOLINTXUBIDEA
- SAN ADRIÁN fte. 48
- SAN ADRIÁN 48
- SAN ADRIÁN fte. 33
- TRAUKO 3
- SAN ADRIÁN 33
- SAN ADRIÁN 36
- SAN ADRIÁN 17
- SAN ADRIÁN 2
- ROTONDA JUAN DE GARAY
- MARTÍN BARÚA 17
- GOIKO TORRE 12
- FLORESTA
- MARTÍN BARÚA fte. 24
- JULIÁN ZUGAZAGOITIA 13
- TRAUKO fte. 5
- GERNIKA 24
- GERNIKA 23
- GENERAL EGUÍA / INTERMODAL
- ESTACIÓN BASURTO
- GERNIKA 10
- HOSPITAL SANTA MARINA
- ETXEARTE
- Fte. ETXEARTE
- MIKOLETA
- Fte. MIKOLETA
- ORUETA
- Fte. ORUETA
- GERNIKA 11
- GERNIKA 1
- GORDÓNIZ 90
- CIRCUNVALACIÓN 1
- CIRCUNVALACIÓN 12
- XENPELAR / TRAVESÍA ZABALA
- URETAMENDI
- XENPELAR / ZABALA
- JUAN DE GARAY 33
- JUAN DE GARAY 11
- ZABALA 22
- TRAUKO 14
- Dr. FLEMING 1
- ATXETABIDEA 47
- CORTES 23
- CORTES 13
- PLAZA CIRCULAR
- GRAN VÍA 7
- GRAN VÍA 8
- MONTE IZARO 8
- IBÁÑEZ DE BILBAO 14
- GRAN VÍA 37
- GUGGENHEIM
- GRAN VÍA 74
- IPARRAGUIRRE fte. 42
- SAN VALENTÍN DE BERRIOTXOA
- HURTADO DE AMÉZAGA 1
- HURTADO DE AMÉZAGA 2
- MAZARREDO 3
- ALAMEDA RECALDE 11
- ALAMEDA RECALDE 12
- ALAMEDA RECALDE 31
- GRAN VÍA 36
- ELCANO fte. 9
- PLAZA ELÍPTICA 4
- GRAN VÍA 41
- MAURICE RAVEL / CIUDAD JARDÍN
- PALACIO CHÁVARRI
- GRAN VÍA 43
- ELCANO 3
- IPARRAGUIRRE 29
- ELCANO 2
- MUSEO PLAZA 5
- PUENTE DE DEUSTU
- LA ROSETA
- and 282 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
9 findings, ordered by severity.
Show every finding
- Error1 instance
Invalid row length (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_row_length · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning508 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning245 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning245 instances
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unused_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
1 of 532 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info422 instances
About 422 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · 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. 1 validator error to resolve.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 298 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
- 245 of 15224 trips list fewer than two stops. A trip with one stop has no ride in it. Trip planners can't put a rider on that trip at all. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
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 298 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
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 54 / 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 88 / 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/bilbobus/2026-09-05.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-09-05. 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.