GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

CRTM — Red de Metro Ligero (Madrid light rail)

Based on the feed this agency publishes

Service mode Tram

70.9 / 100

First scorecard for this agency

Catalogued in Madrid, Comunidad de, Spain.

Covers 339 daysRealtime not yet published

The Madrid region's light rail network as published by the regional transport consortium; a distinct published feed from the same organization as the city bus record.

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

Fix 01

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

Fix 02

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

Fix 03

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

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.

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

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

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

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 339 days.
Published accessibility data
Accessibility information is stated for 74% 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

Correctness70.8 / 100

The MobilityData validator flagged 7 kinds of issue across 6178 instances (0 error, 6162 warning, 16 informational).

Freshness85.0 / 100

Service data covers the next 339 days.

Rider experience59.9 / 100

74% of stops state wheelchair accessibility (0% marked accessible, 74% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility83.7 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (ML1, ML3, ML4).

    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.

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

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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • ML1 (teal)
  • ML2 (purple)
  • ML3 (red)
  • ML4 (brown)
Routes in CRTM — Red de Metro Ligero (Madrid light rail)'s feed
RouteTypeLine color
ML1 Pinar de Chamartín - Las TablasTram / light railteal
ML2 Colonia Jardín - Estación de AravacaTram / light railpurple
ML3 Colonia Jardín - Puerta de BoadillaTram / light railred
ML4 Tranvía de Parla (Línea Circular)Tram / light railbrown

This feed has 96 stops.

List every stop
  • Somosaguas Sur
  • Ascensor
  • Arturo Soria
  • Ascensor
  • Avenida de Europa
  • Ascensor
  • Berna
  • Ascensor
  • Ascensor
  • Montepríncipe
  • Avda. Fuente de la Mora
  • Ascensor
  • Camino Fuente de la Mora
  • Ascensor
  • Avda. Manoteras
  • Ascensor
  • Príncipe Carlos
  • Príncipe Carlos
  • Príncipe Carlos
  • Ascensor
  • María Tudor
  • Ascensor
  • Catalina de Austria
  • Palas de Rey
  • Palas de Rey
  • PINAR DE CHAMARTIN
  • COLONIA JARDIN
  • SOMOSAGUAS SUR
  • FUENTE DE LA MORA
  • AVENIDA DE EUROPA
  • BERNA
  • MONTEPRINCIPE
  • VIRGEN DEL CORTIJO
  • ANTONIO SAURA
  • ALVAREZ DE VILLAAMIL
  • BLASCO IBAÑEZ
  • MARIA TUDOR
  • PALAS DE REY
  • LAS TABLAS
  • PINAR DE CHAMARTIN
  • COLONIA JARDIN
  • PRADO DE LA VEGA
  • COLONIA DE LOS ANGELES
  • PRADO DEL REY
  • SOMOSAGUAS SUR
  • SOMOSAGUAS CENTRO
  • POZUELO OESTE
  • BELGICA
  • DOS CASTILLAS
  • FUENTE DE LA MORA
  • CAMPUS DE SOMOSAGUAS
  • AVENIDA DE EUROPA
  • BERNA
  • ESTACION DE ARAVACA
  • COLONIA JARDIN
  • CIUDAD DE LA IMAGEN
  • JOSE ISBERT
  • CIUDAD DEL CINE
  • RETAMARES
  • MONTEPRINCIPE
  • VIRGEN DEL CORTIJO
  • VENTORRO DEL CANO
  • PRADO DEL ESPINO
  • CANTABRIA
  • FERIAL DE BOADILLA
  • BOADILLA CENTRO
  • NUEVO MUNDO
  • SIGLO XXI
  • INFANTE DON LUIS
  • PUERTA DE BOADILLA
  • COCHERAS
  • ANTONIO SAURA
  • ALVAREZ DE VILLAAMIL
  • PLAZA DE TOROS
  • JULIO ROMERO DE TORRES
  • LA BALLENA
  • PARLA CENTRO - BULEVAR NORTE
  • IGLESIA CENTRO
  • BULEVAR SUR
  • REYES CATOLICOS
  • ISABEL II
  • PARQUE PARLA ESTE
  • AVENIDA SISTEMA SOLAR
  • BLASCO IBAÑEZ
  • TIERRA NORTE
  • TIERRA SUR
  • VENUS NORTE
  • VENUS SUR
  • ESTRELLA POLAR NORTE
  • ESTRELLA POLAR SUR
  • JAIME I NORTE
  • JAIME I SUR
  • POLIGONO INDUSTRIAL CIUDAD DE PARLA
  • MARIA TUDOR
  • PALAS DE REY
  • LAS TABLAS

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

13 findings, ordered by severity.

Show every finding
  • Warning6065 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.)

    Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning92 instances

    Equal shape distance same coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning25 instances

    25 of 96 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

  • Warning2 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

  • 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.)

    Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Missing feed contact email and url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt is missing its start/end dates

    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

  • 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

  • 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

  • Info71 instances

    About 71 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.)

    Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info13 instances

    Unused station (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: unused_station · See MobilityData GTFS Validator rules

  • Info3 instances

    Big gap in service (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 74% of stops and 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 339 days.
Accessible Not yet
States wheelchair access on 74% of stops and 100% 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 339 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 71 / 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 85 / 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 60 / 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.

CRTM — Red de Metro Ligero (Madrid light rail) GTFS data quality grade: C

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/crtm-metro-ligero/2026-07-18.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-18. 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.