Feed status · checked 2026-08-31
TRAM Barcelona (Trambesòs)
Based on the official feed source on file
Service mode Tram + Other
unchanged since 2026-08-30
Catalogued in Barcelona [Barcelona], 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.
Checked for changes 3 hours ago; last changed 14 days 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.
Top things to fix
Review the rule documentation for 'invalid_integer' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid integer (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid date (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 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 integer (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_integer' 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
- Invalid date (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_date' 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
- Invalid url (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_url' 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
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_integer' 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. See this feed's finding-clearance log.
Review the rule documentation for 'invalid_date' 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. See this feed's finding-clearance log.
Review the rule documentation for 'invalid_url' 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. 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 122 days.
- Published accessibility data
- Accessibility information is stated for 98.3% of stops and 100% 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 10 kinds of issue across 41 instances (37 error, 4 warning, 0 informational).
Service data covers the next 122 days.
98% of stops state wheelchair accessibility (98% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
98% of stops state accessibility (98% marked accessible). Reflects what the feed states, 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.
This feed has 57 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.
- T1 (green)
- T2 (green)
- T3 (green)
- T4 (green)
- T5 (green)
- T6 (green)
| Route | Type | Line color |
|---|---|---|
| T1 Bon Viatge-Francesc Macià | Tram / light rail | green |
| T2 Llevant_Les Planes-Francesc Macià | Tram / light rail | green |
| T3 Sant Feliu|Consell Comarcal-Francesc Macià | Tram / light rail | green |
| T4 Estació de Sant Adrià-Verdaguer | Tram / light rail | green |
| T5 Gorg-Ciutadella|Vila Olímpica | Tram / light rail | green |
| T6 Estació de Sant Adrià-Ciutadella|Vila Olímpica | Tram / light rail | green |
| route_short_name route_long_name | Transit line | green (no shape in feed) |
List every stop
- Francesc Macià
- Campus Diagonal - Besòs
- Avinguda de Xile
- La Mina
- Ernest Lluch
- Can Rigal
- La Catalana
- Ca n'Oliveres
- Can Clota
- Sant Joan Baptista
- Pont d'Esplugues
- La Sardana
- Encants de Sant Adrià
- Montesa
- Sant Roc
- El Pedró
- Ignasi Iglésias
- Gorg
- Cornellà Centre
- Auditori | Teatre Nacional
- L'Illa
- Ciutadella | Vila Olímpica
- Les Aigües
- Fontsanta | Fatjó
- Marina
- Bon Viatge
- Can Jaumandreu
- Espronceda
- Sant Martí de Provençals
- La Fontsanta
- Besòs
- Centre Miquel Martí i Pol
- Alfons el Magnànim
- Parc del Besòs
- Hospital Sant Joan Despí | TV3
- Port Fòrum
- Rambla de Sant Just
- Glòries
- Numància
- Estació de Sant Adrià
- Walden
- Torreblanca
- Monumental
- Sant Feliu | Consell Comarcal
- Sicília
- Verdaguer
- Ca l'Aranyó
- Maria Cristina
- Pere IV
- Pius XII
- Fluvià
- Selva de Mar
- El Maresme
- Palau Reial
- Fòrum
- Zona Universitària
- Llevant - Les planes
Over time
Overall score across the last 5 checks — unchanged since 2026-08-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 54.3 | first check |
| 2026-08-07 | 54.3 | no change |
| 2026-08-10 | 52.7 | down 1.6 |
| 2026-08-30 | 49.2 | down 3.5 |
| 2026-08-31 | 49.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-08-10 feed renewed to a current calendar. On 2026-08-31 the check no longer reported: a file GTFS asks for (usually feed_info.txt) is missing; same name and description for route (flagged by the MobilityData validator); same name and description for stop (flagged by the MobilityData validator); feed_info.txt is missing its start/end dates (the file itself is absent); feed_info.txt has no technical contact (feed_contact_email or feed_contact_url); this feed models stations or entrances but has no pathways.txt. As of 2026-08-31 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-30 Score fell 4 points, correctness fell 84 points.
- 2026-08-10 Feed renewed to a current calendar.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error15 instances
Invalid integer (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_integer' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_integer · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error5 instances
Invalid date (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error5 instances
Invalid url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error4 instances
Invalid float (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_float' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_float · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Invalid color (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_color' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_color · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Invalid language code (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_language_code' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_language_code · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Invalid time (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid timezone (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_timezone' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_timezone · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning16872 instances
16872 of 34725 trips have no headsign, the text that tells riders where the transit vehicle is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning4 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
1 of 58 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)
- Warning1 instance
1 of 34725 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 · See GTFS Schedule reference (opens the GTFS Schedule reference 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. 9 validator errors to resolve.
- Valid Not yet
- 9 validator errors to resolve.
- Current Met
- Service data covers the next 122 days.
- Accessible Met
- States wheelchair access on 98% 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.
- 1 of 34725 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 121 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 37 validator errors, 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 0 / 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 77 / 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/tram-barcelona-tbs/2026-08-31.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-08-31. 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.