← All agencies

Feed status · checked 2026-10-13

Metro Bilbao

Based on the official feed source on file

Service mode Metro

FDCBA

63.2 / 100

up 1.7 since 2026-10-12 · D → D

Cataloged in Bizkaia, Spain.

Covers 30 daysAccessibility gapsRealtime not yet published

Source feed: https://ctb-gtfs.s3.eu-south-2.amazonaws.com/metrobilbao.zip Version history on the Mobility Database

MDB 3052 is the active replacement for deprecated records 2683 and 1200; the predecessors are not separate feed coverage.

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 68 minutes ago; last changed 68 minutes 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

Metro Bilbao’s published feed lists 1 subway / metro route, 4,613 scheduled trips and 191 stops. The published file last changed on 2026-10-13.

Top things to fix

Fix 01

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.

Fixing this covers all 191 stops in the feed.

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

Fix 02

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

4613 of 4613 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.

Fixing this covers all 4,613 trips in the feed.

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

Fix 03

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.

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

⏱ Two fields, set once in export settings.worth about +15 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.
The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

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

Agency: Metro Bilbao
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 191 of 191 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest 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.
Evidence: https://gtfsscorecard.org/agency/metro-bilbao/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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.

Fix 01 · 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.
Fix 02 · 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.
Fix 03 · Read the fix guide for scorecard_missing_feed_info_dates
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 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.

Hi,

Our GTFS feed (Metro Bilbao) scored D (63.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 191 of 191 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 4613 of 4613 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Add feed_info.txt with feed_start_date and feed_end_date to your export.
   What: feed_info.txt is missing its start/end dates (the file itself is absent)
   Finding code: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

Full scorecard: https://gtfsscorecard.org/agency/metro-bilbao/

Score by category

Correctness87.0 / 100

The MobilityData validator flagged 4 kinds of issue across 527 instances (0 error, 4 warning, 523 informational).

Freshness35.0 / 100

Service data covers the next 30 days.

Rider experience52.5 / 100

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.

Accessibility0 / 100

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

FaresLegacy fares

Fares are applied to trips.

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 191 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.

Línea De Metro Bilbao (orange)

Routes in Metro Bilbao's feed
Route	Type	Line color
Línea De Metro Bilbao	Subway / metro	orange

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

Overall score across the last 3 checks — up 1.7 since 2026-10-12.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-11	63.2	first check
2026-10-12	61.5	down 1.7
2026-10-13	63.2	up 1.7

What changed since your last check

Correctness up 4.0
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
Checked	Published file	Service dates through	Grade at the time
2026-10-13	`e83ffdb425e6`	2026-11-12	Current rubric: see the trend above
2026-10-12	`4ecadcebcfb1`	2026-11-11	Current rubric: see the trend above
2026-10-11	`54e2b0bb5e39`	2026-11-10	Current rubric: see the trend above
2026-09-13	`9722d2c22e67`	2026-10-12	D, 61.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-01	`16b7fce9bfb4`	2026-09-30	D, 64.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-06 to 2026-08-07 (2 checks)	`4d3a04f47887`	2026-09-05	D, 61.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall score rose 1.7 points since 2026-10-12.

The feed file was re-published since 2026-10-12 (-96 KB).

What changed inside the export

Service now runs through 2026-11-12 (was 2026-11-11).

Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.

Changed counts

down 4613 of 4613 trips don't say whether the vehicle is wheelchair accessible. (5015 → 4613) (scorecard_wheelchair_accessible_unknown)
down Unsorted stop times (flagged by the MobilityData validator). (629 → 523) (unsorted_stop_times)

No longer reported since 2026-10-12 (1 finding)

Many of the feed's trips don't run at all in the next 7 days. (trip_coverage_not_active_for_next7_days)

This records the later feed state. It does not establish who made a change or why.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

9 findings, ordered by severity.

Show every finding

Warning4613 instances
4613 of 4613 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.)
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)
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.)
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)
Warning2 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
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
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
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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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 to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Info523 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.)
Finding code: 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).
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

Two requirements remain for this feed to earn 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 87 / 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.

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

Similar feeds in Bizkaia

Other scorecards in Bizkaia, 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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/metro-bilbao/"><img src="https://gtfsscorecard.org/agency/metro-bilbao/badge.svg" width="320" height="58" alt="Metro Bilbao: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Metro Bilbao: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/metro-bilbao/badge.svg)](https://gtfsscorecard.org/agency/metro-bilbao/)

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-10-13.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-13. 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.

GTFS Scorecard. (2026). Metro Bilbao GTFS feed-quality record, dated 2026-10-13 (grade D (63.2/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 e83ffdb425e6…). https://gtfsscorecard.org/data/artifacts/metro-bilbao/2026-10-13.json

@misc{gtfsscorecard-metro-bilbao-2026-10-13,
  title        = {Metro Bilbao GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/metro-bilbao/2026-10-13.json}},
  note         = {Checked 2026-10-13; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (63.2/100)}
}

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