Feed status · checked 2026-07-17
Metro Bilbao
Based on the feed this agency publishes
Service mode Metro
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.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
191 of 191 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
7008 of 7008 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.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 feed_info.txt with feed_start_date and feed_end_date to your export. · 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 30 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
- 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 3 kinds of issue across 876 instances (0 error, 2 warning, 874 informational).
Service data covers the next 30 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
10 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Zazpikaleak/Casco Viejo", "Gurutzeta/Cruces", "96 (Zazpikaleak/Casco Viejo)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Línea De Metro Bilbao (orange)
| Route | Type | Line color |
|---|---|---|
| Línea De Metro Bilbao | Subway / metro | orange |
This feed has 191 stops.
List every stop
- Ariz
- Ariz
- 40 (Ariz)
- 41 (Ariz)
- 42 (Ariz)
- San Mamés
- San Mamés
- 207 (San Mamés)
- 208 (San Mamés)
- 209 (San Mamés)
- Deustu
- Deustu
- 104 (Deustu)
- 105 (Deustu)
- 106 (Deustu)
- Sarriko
- Sarriko
- 222 (Sarriko)
- San Ignazio
- San Ignazio
- 237 (San Ignazio)
- 238 (San Ignazio)
- 239 (San Ignazio)
- 240 (San Ignazio)
- 241 (San Ignazio)
- Lutxana
- Lutxana
- 168 (Lutxana)
- 169 (Lutxana)
- Erandio
- Erandio
- 111 (Erandio)
- Astrabudua
- Astrabudua
- 47 (Astrabudua)
- 48 (Astrabudua)
- Leioa
- Leioa
- 163 (Leioa)
- 164 (Leioa)
- Lamiako
- Lamiako
- 152 (Lamiako)
- 153 (Lamiako)
- 275 (Lamiako)
- Areeta
- Areeta
- 33 (Areeta)
- 34 (Areeta)
- 35 (Areeta)
- Etxebarri
- Etxebarri
- 115 (Etxebarri)
- 116 (Etxebarri)
- Gobela
- Gobela
- 120 (Gobela)
- Neguri
- Neguri
- 183 (Neguri)
- 184 (Neguri)
- Aiboa
- Aiboa
- 16 (Aiboa)
- 17 (Aiboa)
- Algorta
- Algorta
- 21 (Algorta)
- 22 (Algorta)
- 23 (Algorta)
- Bidezabal
- Bidezabal
- 78 (Bidezabal)
- 79 (Bidezabal)
- 80 (Bidezabal)
- Ibarbengoa
- Ibarbengoa
- 132 (Ibarbengoa)
- 276 (Ibarbengoa)
- Berango
- Berango
- 74 (Berango)
- Larrabasterra
- Larrabasterra
- 158 (Larrabasterra)
- 159 (Larrabasterra)
- Sopela
- Sopela
- 247 (Sopela)
- 248 (Sopela)
- Urduliz
- Urduliz
- 265 (Urduliz)
- 272 (Urduliz)
- Bolueta
- Bolueta
- 84 (Bolueta)
- 85 (Bolueta)
- Plentzia
- Plentzia
- 196 (Plentzia)
- Gurutzeta/Cruces
- Gurutzeta/Cruces
- 124 (Gurutzeta/Cruces)
- 125 (Gurutzeta/Cruces)
- 126 (Gurutzeta/Cruces)
- Ansio
- Ansio
- 28 (Ansio)
- Barakaldo
- Barakaldo
- 60 (Barakaldo)
- 61 (Barakaldo)
- 62 (Barakaldo)
- 63 (Barakaldo)
- Bagatza
- Bagatza
- 53 (Bagatza)
- 54 (Bagatza)
- 55 (Bagatza)
- Urbinaga
- Urbinaga
- 261 (Urbinaga)
- Sestao
- Sestao
- 229 (Sestao)
- 230 (Sestao)
- 231 (Sestao)
- 232 (Sestao)
- Abatxolo
- Abatxolo
- 10 (Abatxolo)
- 11 (Abatxolo)
- 9 (Abatxolo)
- Portugalete
- Portugalete
- 200 (Portugalete)
- 201 (Portugalete)
- 202 (Portugalete)
- Basarrate
- Basarrate
- 68 (Basarrate)
- 69 (Basarrate)
- Peñota
- Peñota
- 189 (Peñota)
- 190 (Peñota)
- 191 (Peñota)
- Santurtzi
- Santurtzi
- 253 (Santurtzi)
- 254 (Santurtzi)
- 255 (Santurtzi)
- 256 (Santurtzi)
- Kabiezes
- Kabiezes
- 143 (Kabiezes)
- 144 (Kabiezes)
- 145 (Kabiezes)
- Santutxu
- Santutxu
- 215 (Santutxu)
- 216 (Santutxu)
- 217 (Santutxu)
- Basauri
- Basauri
- 89 (Basauri)
- 90 (Basauri)
- 91 (Basauri)
- Zazpikaleak/Casco Viejo
- Zazpikaleak/Casco Viejo
- 96 (Zazpikaleak/Casco Viejo)
- 97 (Zazpikaleak/Casco Viejo)
- 98 (Zazpikaleak/Casco Viejo)
- Abando
- Abando
- 1 (Abando)
- 2 (Abando)
- 3 (Abando)
- 4 (Abando)
- Eliptikoa
- Eliptikoa
- 175 (Eliptikoa)
- 176 (Eliptikoa)
- 177 (Eliptikoa)
- 178 (Eliptikoa)
- Indautxu
- Indautxu
- 136 (Indautxu)
- 137 (Indautxu)
- 138 (Indautxu)
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
8 findings, ordered by severity.
Show every finding
- Warning7008 instances
7008 of 7008 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning191 instances
191 of 191 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)
- 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info874 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. Service data runs out in 30 days; renew to qualify. 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 Not yet
- Service data runs out in 30 days; renew to qualify.
- 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 30 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 91 / 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 35 / 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 52 / 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/metro-bilbao/2026-07-17.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-17. 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.