← All agencies

Feed status · checked 2026-09-05

CRTM — Red de Autobuses Urbanos (Madrid regional urban bus)

Based on the official feed source on file

Service mode Bus

33.8 / 100

First scorecard for this agency

Catalogued in Madrid, Comunidad de, Spain.

Covers 355 daysAccessibility gapsRealtime not yet published

The urban bus networks of municipalities across the Madrid region other than the capital, published by the regional transport consortium as one of its separately published network feeds.

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

Fix 01

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

Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +18 points in its category

Fix 02

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

Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +18 points in its category

Fix 03

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

14230 of 14230 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 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
Equal shape distance diff coordinates (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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.

  1. Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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.

  2. Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' 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.

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

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 355 days.
Published accessibility data
Accessibility information is stated for 70.9% of stops and 0% 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

Correctness0.0 / 100

The MobilityData validator flagged 16 kinds of issue across 48214 instances (20 error, 48181 warning, 13 informational).

Freshness85.0 / 100

Service data covers the next 355 days.

Rider experience40.3 / 100

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

Accessibility44.3 / 100

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

2 accessibility depth signals

  • 2663 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("AV.LOYOLA-PZA.MATADERO", "AV.LOYOLA-PZA.MATADERO", "AV.LOYOLA-PZA.PALOMA", 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.

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 8406 stops.

Skip to route and stop data

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.

  • 10 (red)
  • 10 (red)
  • 11 (red)
  • 11 (red)
  • 1A (red)
  • 1A (red)
  • 1A (red)
  • 1A (red)
  • 1B (red)
  • 1B (red)
  • 1B (red)
  • 1B (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 1 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 2 (red)
  • 3B (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 3 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 4 (red)
  • 5A (red)
  • 5B (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 5 (red)
  • 6 (red)
  • 6 (red)
  • 6 (red)
  • 6 (red)
  • 6 (red)
  • 6 (red)
  • 6 (red)
  • 7 (red)
  • 7 (red)
  • 7 (red)
  • 7 (red)
  • 8 (red)
  • 8 (red)
  • 9 (red)
  • 9 (red)
  • PI1 (red)
  • PI2 (red)
  • SE (red)
Routes in CRTM — Red de Autobuses Urbanos (Madrid regional urban bus)'s feed
RouteTypeLine color
10 VIA COMPLUTENSE CENTRO - ESPARTALES NORTEBusred
10 CIRCULAR DE ALCOBENDASBusred
11 LA GARENA - EST. ALCALÁ UNIVERSIDADBusred
11 CIRCULAR DE ALCOBENDASBusred
1A CIRCULAR ALCALÁ DE HENARESBusred
1A CIRCULAR ARROYOMOLINOSBusred
1A CIRCULAR PINTOBusred
1A CIRCULAR TORREJÓNBusred
1B CIRCULAR ALCALÁ DE HENARESBusred
1B CIRCULAR ARROYOMOLINOSBusred
1B CIRCULAR PINTOBusred
1B CIRCULAR TORREJÓNBusred
1 ARROYO DE LA VEGA-EL SOTO-LA MORALEJABusred
1 PUERTA DEL SUR - FUENTE CISNEROSBusred
1 L1 CIRCULAR (FFCC-Moreras-FFCC)Busred
1 RESIDENCIA-LA POVEDABusred
1 PASEO DE MADRID-OLIVAR-PARQUE-LAS LOMASBusred
1 HOSPITAL DE LA FUENFRÍA - FF.CC. - INSTITUTOBusred
1 CIRCULAR DE CIEMPOZUELOSBusred
1 EST. COMENAR VIEJO - LAS ADELFILLASBusred (no shape in feed)
1 FFCC-PQUE. CORUÑA-LOS VALLES-PUEBLO-URBANIZACIONESBusred
1 SECTOR III-AMBULATORIOBusred
1 CIRCULAR VEREDA DE LOS ESTUDIANTES-LA FORTUNABusred
1 CIRCULAR (Hospital-Estación FFCC)Busred
1 LAS CUMBRES-ESTACIÓN FFCCBusred
1 LA DEHESA-EL PINARBusred
1 URB. ALTOS DE JARAMA - MIRAMADRIDBusred
1 CIRCULAR 1Busred
1 PEDREZUELA-URBANIZACIONESBusred
1 POZUELO DE ALARCÓN-URB. LA CABAÑABusred
1 BARRIO DE LA LUNA - RIVAS PUEBLOBusred
1 LAS ROZAS-URBANIZACIÓN MOLINO DE LA HOZBusred
1 POL. INDUSTRIAL-C.C. SAN FERNANDOBusred
1 S. L. DE EL ESCORIAL-FFCC-S. L. DE EL ESCORIALBusred
1 CIRCULAR SAN MARTIN DE LA VEGABusred (no shape in feed)
1 FFCC-PUEBLO-ÁREA HOMOGÉNEA SURBusred
1 CIRCULAR (FFCC-Ambulatorio-FFCC)Busred
1 FFCC-AVENIDA VIÑUELAS-AVENIDA COLMENAR-FFCCBusred
2 PUERTA DE SANTA ANA - HOSPITAL/UNIVERSIDADBusred
2 ALCOBENDAS-LA MORALEJABusred
2 ONDARRETA-PRADO STO DOMINGOBusred
2 L2 CIRCULAR (FFCC-Residencia-FFCC)Busred
2 LA POVEDA-SIETE VIENTOS-HOSPITALBusred
2 FERIAL DE BOADILLA-VALDEPASTORES-LAS LOMASBusred
2 EST. COLMENAR VIEJO - AV. REMEDIOSBusred (no shape in feed)
2 FFCC-PQUE. CORUÑA-CENTRO SALUD-LOS NEGRALES-FFCCBusred
2 BARRIO DE LA ESTACIÓN-CENTRO DE TRANSPORTESBusred
2 ARROYO CULEBRO - AMBULATORIOBusred
2 CIRCULAR (Hospital-Estación FFCC)Busred
2 MÓSTOLES (Pradillo)-CEMENTERIOBusred
2 PICÓN DEL CURA - URB. LOS BERROCALESBusred
2 CIRCULAR 2Busred
2 CIRCULAR DE POZUELO DE ALARCÓNBusred
2 LAS ROZAS - MONTE ROZAS - EL ENCINARBusred
2 EL ESCORIAL-SAN LORENZO DE EL ESCORIAL-HOSPITAL-LA PIZARRABusred
2 FRONTERAS-BARRIO CASTILLO-FRESNOBusred
2 FFCC-AVENIDA DEHESA-LOS ROBLESBusred
2 ESTACIÓN FFCC-EL RESTÓNBusred
2 FFCC-AVENIDA COLMENAR-AVENIDA VIÑUELAS-FFCCBusred
3A CIRCULAR DE GETAFEBusred (no shape in feed)
3B CIRCULAR DE GETAFEBusred
3 CUATRO CAÑOS - HOSPITAL/UNIVERSIDAD - ESPARTALESBusred
3 ARROYO DE LA VEGA-SOTO DE LA MORALEJA-EL ENCINAR DE LOS REYESBusred
3 ALCORCÓN CENTRAL - PARQUE EL LUCEROBusred
3 L3 CIRCULAR (FFCC-Glorieta de la Música-FFCC)Busred
3 FERIAL DE BOADILLA-VALDECABAÑAS-BONANZABusred
3 FF.CC. - EL GORRONAL - HOSPITALBusred
3 EL ESCORIAL-LAS ZORRERASBusred
3 POLÍGONO INDUSTRIAL LAS NIEVES-MÓSTOLES PRADILLOBusred
3 HOSPITAL-AVENIDA DE AMÉRICA-LAGUNA PARKBusred
3 CIRCULAR DE POZUELO DE ALARCÓNBusred
3 LOS FRESNOS - PLAZA DE ESPAÑA - LOS ALMENDROSBusred
3 CIRCULAR (El Restón-Avenida Andalucía-El Restón)Busred
3 SOTO DE VIÑUELAS-TRES CANTOS FFCC-SOTO DE VIÑUELASBusred
4 EST. ARANJUEZ - HOSPITAL - PAU DE LA MONTAÑABusred
4 CIRCULAR ARGANDABusred
4 BOADILLA CENTRO - EL PASTELBusred
4 FFCC-PQUE. CORUÑA-PUEBLOBusred
4 POL. IND. LOS ÁNGELES - HOSPITAL - PERALES DEL RÍOBusred
4 POLIDEPORTIVO-VALLEFRESNOS/LA SERRANILLABusred
4 MÓSTOLES SUR - MÓSTOLES (HOSPITAL REY JUAN CARLOS)Busred
4 CIRCULAR SAN LORENZO DE EL ESCORIALBusred
4 POLIDEPORTIVO-MOSCATELARESBusred
4 TORREJÓN-PARQUE CORREDORBusred
4 FFCC-PUEBLO-LOS PEÑASCALESBusred
4 ESTACIÓN FFCC-POLÍGONOS NORTEBusred
4 TRES CANTOS NORTE - TRES CANTOS FF.CC.Busred
5A CIRCULAR PARQUE EUROPABusred
5B CIRCULAR PARQUE EUROPABusred
5 PLAZA DE LA PAZ - NUEVA RINCONADABusred
5 S. S. DE LOS REYES-ALCOBENDAS-SOTO MORALEJABusred
5 L5 CIRCULAR (FFCC-La Montaña-FFCC)Busred
5 BUENAVISTA - SECTOR IIIBusred
5 MOSTOLES (Estación FF.CC.) - PARQUE COIMBRABusred
5 FFCC-PUEBLO-LOS PEÑASCALES (Por Pº Joaquín Ruiz J.)Busred
5 ESTACIÓN FFCC-P.I. ROMPECUBASBusred
5 TRES CANTOS NORTE - AV. VIÑUELASBusred
6 EST. LA GARENA - VIRGEN DEL VALBusred
6 ESTACIÓN FFCC VALDELASFUENTES-POLG. INDUSTRIALBusred
6 FFCC-CANTOS ALTOS-PUEBLO-ARROYO ARRIBABusred
6 HOSPITAL - SAN ISIDROBusred
6 UNIVERSIDAD REY JUAN CARLOS-URB. P.GUADARRAMABusred
6 PLAZA DE ESPAÑA - OASIZBusred
6 ESTACIÓN FFCC-EL CARACOL-EL RESTÓN IIBusred
7 ENSANCHE NORTE - NUEVA ALCALÁ / CEMENTERIO JARDÍNBusred
7 7 CIRCULAR GETAFE CENTRAL - TECNOGETAFEBusred
7 ESTACIÓN FFCC-POLÍGONOS-ESTACIÓN FFCCBusred
7 ESTACIÓN FFCC-HOSPITAL-EL RESTÓNBusred
8 LOS NOGALES - VIRGEN DEL VALBusred
8 CIRCULAR CIUDALCAMPOBusred
9 EST. ALCALÁ DE HENARES - EL OLIVAR /POLÍGONO CAMPORROSOBusred
9 ESTACIÓN FFCC-ARROYO DE LA VEGABusred
I1 INSTITUTO ALGETEBusred (no shape in feed)
PI1 GETAFE CENTRAL - P.I. LOS ANGELES - P.I. LOS OLIVOSBusred
PI2 GETAFE CENTRAL-P.I. SAN MARCOS-P.I. EL LOMO-P.E. LA CARPETANÍABusred
SE SE URBANA VALDEMOROBusred
i1 RUTAS INSTITUTOSBusred (no shape in feed)
List every stop
  • Aluche
  • Méndez Álvaro Estación Sur
  • Intercambiador de Moncloa
  • Intercambiador de Príncipe Pío
  • Intercambiador de Plaza de Castilla
  • Aeropuerto T4
  • Aeropuerto T1 - T2 - T3
  • Intercambiador de Plaza Elíptica
  • Intercambiador de Avenida de América
  • INTERCAMBIADOR MONCLOA
  • PRINCESA-MONCLOA
  • AV.JUAN DE LA CIERVA-PZA.LAS HERAS
  • CTRA.HIPÓDROMO-CLUB PUERTA DE HIERRO
  • CTRA.A6-BERMEO
  • AV.PADRE HUIDOBRO-URB.CASAQUEMADA
  • AV.OSA MAYOR-BATALLA DE GARELLANO
  • CAMINO VALLADOLID-PºJOAQUÍN R.JIMÉNEZ
  • CAMINO VALLADOLID-IGLESIA
  • AV.JUAN CARLOS I-ZOCO
  • AV.ASTURIAS-UNIVERSIDAD
  • AV.ASTURIAS-CANGAS DE ONÍS
  • AV.ASTURIAS-RIBADESELLA
  • AV.ASTURIAS-SANTIÁÑEZ
  • RÍO SELLA-AV.ASTURIAS
  • RÍO SELLA-AUSEVA
  • AV.BERZOSA-ARRA
  • AV.PALOMA-FAUSTO MARTÍN
  • PZA.NUESTRA SRA.ROSARIO-PºMAYOR
  • URB.PARQUE LAS COLINAS
  • CTRA.M618-PUERTA 2 CAMPAMENTO
  • AV.PALOMA-FAUSTO MARTÍN
  • AV.BERZOSA-ARRA
  • RÍO SELLA-AUSEVA
  • RÍO SELLA-AV.ASTURIAS
  • AV.ASTURIAS-SANTIÁÑEZ
  • AV.ASTURIAS-RIBADESELLA
  • AV.ASTURIAS-CANGAS DE ONÍS
  • AV.ASTURIAS-UNIVERSIDAD
  • AV.TORRELODONES-URB.LAS MARÍAS
  • MONTE PEREGRINOS-HÍPICA Y GOLF
  • AV.SICILIA-PIAMONTE
  • AV.NORMANDÍA-ALSACIA
  • AV.SAJONIA-AV.TOSCANA
  • AV.BOHEMIA-FUENTES CLARAS
  • CTRA.LA NAVATA-EST.GALAPAGAR LA NAVATA
  • CTRA.LA NAVATA-ERMITA LA NAVATA
  • CTRA.LA NAVATA-SOL
  • CTRA.LA NAVATA-URB.CARRANZA
  • CTRA.LA NAVATA-SAN GREGORIO
  • CTRA.TORRELODONES-CAÑUELO
  • JESUSA LARA-ANTONIO LASSO
  • CTRA.TORRELODONES-URB.LOS JARALES
  • CTRA.TORRELODONES-URB.EL CORZO
  • SOBERANÍA-PZA.CRUZ ROJA
  • PZA.GUIJO-URB.EL GUIJO
  • CTRA.TORRELODONES-CAÑUELO
  • CTRA.TORRELODONES-URB.LOS JARALES
  • CTRA.TORRELODONES-MONTE INÉS
  • CTRA.LA NAVATA-URB.CARRANZA
  • CTRA.LA NAVATA-SOL
  • CTRA.LA NAVATA-ERMITA LA NAVATA
  • CTRA.LA NAVATA-EST.GALAPAGAR LA NAVATA
  • AV.BOHEMIA-FUENTES CLARAS
  • AV.TOSCANA-TEJAS VERDES
  • AV.NORMANDÍA-ALSACIA
  • AV.SICILIA-PIAMONTE
  • MONTE PEREGRINOS-HÍPICA Y GOLF
  • CTRA.A6-ANTONIO LASSO
  • JESUSA LARA-PARQUE PRADOGRANDE
  • AV.TORRELODONES-URB.LAS MARÍAS
  • CTRA.A6-AV.TORRELODONES
  • HUERTOS-CAMINO VALLADOLID
  • CTRA.CORUÑA-CºTOMILLARÓN
  • AV.NOROESTE-SIETE PICOS
  • CTRA.A6-URB.MARACAIBO
  • CTRA.A6-ITV
  • CTRA.A6-URB.PINAR DE LAS ROZAS
  • CTRA.A6-EST.PINAR
  • CTRA.A6-PºTREN TALGO
  • CTRA.A6-URB.PUNTA GALEA
  • GTA.URGULL-MONTE ULIA
  • AV.PEÑASCALES-FRANCISCO ALONSO
  • PZA.FERROCARRIL-EST.LAS MATAS
  • SAN JOSÉ OBRERO-CENTRO COMERCIAL
  • CºGARZO-MAESTRO TURINA
  • ENRIQUE GRANADOS-CºGARZO
  • PºLOS ALEMANES-MIRASIERRA
  • PZA.FERROCARRIL-EST.LAS MATAS
  • PILAR-FRANCISCO ALONSO
  • AV.PEÑASCALES-AV.PARDO
  • AV.MARSIL-CASETA DE GUARDIA
  • CTRA.A6-URB.LOS ÁLAMOS
  • CTRA.A6-TALLERES RENFE
  • CTRA.A6-EST.PINAR
  • CTRA.A6-RESIDENCIA DE ANCIANOS
  • MARÍA GUERRERO-CºCAMPO DE TIRO
  • CTRA.A6-URB.MARACAIBO
  • AV.NOROESTE-PºPINAR
  • AV.DOCTOR TOLEDO-COLEGIO
  • AV.ESPAÑA-URB.LAS CABAÑAS II
  • AV.ESPAÑA-COMUNIDAD DE BALEARES
  • AV.ESPAÑA-COMUNIDAD CASTILLA LEÓN
  • COMUNIDAD ANDALUCÍA-VILLA DE FOZ
  • COMUNIDAD ANDALUCÍA-MAZARRÓN
  • COMUNIDAD LA RIOJA-SERV.SOCIALES
  • AV.IGLESIA-REAL
  • PZA.MADRID-CTRA.CORUÑA
  • CTRA.MAJADAHONDA-BIBLIOTECA
  • CTRA.M505-BURGOCENTRO
  • CTRA.M505-URB.LA CHOPERA
  • CAMINO REAL-URB.MOLINO DE LA HOZ
  • CTRA.M505-URB.RONCESVALLES
  • CTRA.M505-URB.LOS GAMOS
  • CTRA.M505-PZA.CRUZ ROJA
  • CTRA.M505-URB.VISTANEVADA
  • CTRA.M505-URB.VISTANEVADA
  • CTRA.EL ESCORIAL-PZA.CRUZ ROJA
  • CTRA.M505-URB.LOS GAMOS
  • CTRA.M505-URB.RONCESVALLES
  • CTRA.M505-URB.MOLINO DE LA HOZ
  • CTRA.M505-URB.LA CHOPERA
  • CTRA.M505-BURGOCENTRO
  • ESTACIÓN SUR DE AUTOBUSES
  • CTRA.EL ESCORIAL-QUINTA DEL SOL
  • CTRA.A6-COLONIA VERACRUZ
  • COMUNIDAD CASTILLA LA MANCHA-AV.ESPAÑA
  • AV.ESPAÑA-COMUNIDAD DE CANARIAS
  • AV.ESPAÑA-URB.LAS CABAÑAS II
  • AV.GUADARRAMA-AV.REYES CATÓLICOS
  • FRANCISCO UMBRAL-LAS VIÑAS
  • AV.DOCTOR MARAÑÓN-PZA.LAGUNA VIEJA
  • CTRA.M509-URB.VILLAFRANCA DEL CASTILLO
  • AV.CASTILLOS-CASTILLO DE ANDRADE
  • CASTILLO ANTEQUERA-CASTILLO BARCIENCE
  • CASTILLO ANTEQUERA-COLEGIO INTERNACIONAL
  • CASTILLO ANTEQUERA-CASTILLO MALPICA
  • VALLE DEL RONCAL-CONSULTORIO MÉDICO
  • VALLE DEL RONCAL-Nº39
  • VALLE DE LA OROTAVA-URB.MOCHA CHICA
  • PIEDRAS VIVAS-URB.PIEDRAS VIVAS
  • VALLE DEL RONCAL-CONSULTORIO MÉDICO
  • CASTILLO ANTEQUERA-CASTILLO MALPICA
  • AV.CASTILLOS-CENTRO COMERCIAL
  • CTRA.M509-URB.SANTA MARÍA
  • CTRA.M509-AV.LOS PINOS
  • BARRANCAS-EMPEDRADA
  • CTRA.M509-LOS PINOS
  • AV.MADRID-RECAUDACIÓN
  • AV.MADRID-ADOLFO SUÁREZ
  • CTRA.M509-URB.SANTA MARÍA
  • AV.DOCTOR MARAÑÓN-PZA.LAGUNA VIEJA
  • AV.GUADARRAMA-AV.REYES CATÓLICOS
  • AV.PEÑASCALES-AV.PARDO
  • AV.ESPAÑA-COMUNIDAD CASTILLA LA MANCHA
  • AV.REYES CATÓLICOS-AV.GUADARRAMA
  • AV.REYES CATÓLICOS-PZA.CRUZ
  • AV.REYES CATÓLICOS-COLOMBIA
  • AV.REYES CATÓLICOS-AV.ESPAÑA
  • CTRA.A6-URB.JARDÍN DE LAS AVENIDAS
  • AV.VICTORIA-VIRGEN DE LOS OLMOS
  • AV.VICTORIA-SAIZ DE LA CALLEJA
  • AV.VICTORIA-CIMARRA
  • AV.VICTORIA-FEDERICO AGUSTI
  • AV.VICTORIA-AV.ESTACIÓN
  • CTRA.PLANTÍO-CLUB DE TENIS
  • CTRA.PLANTÍO-LOS SAUCES
  • CTRA.PLANTÍO-NOVOTIENDAS
  • CTRA.PLANTÍO-CERRO DEL AIRE
  • DOCTOR CALERO-NICARAGUA
  • DOCTOR CALERO-JARDINILLOS
  • AV.REYES CATÓLICOS-PANAMÁ
  • COMUNIDAD CASTILLA LA MANCHA-BURGOCENTRO
  • AV.GUADARRAMA-CENTRO DE ESPECIALIDADES
  • AV.DOCTOR MARAÑÓN-SAN ROQUE
  • AV.ESPAÑA-EL ZOCO
  • CTRA.BOADILLA-CEMENTERIO
  • AV.REYES CATÓLICOS-STA.BEATRÍZ DE SILVA
  • REYES CATÓLICOS-RAMÓN Y CAJAL
  • DOCTOR CALERO-JARDINILLOS
  • DOCTOR CALERO-FUNDADORES
  • CTRA.PLANTÍO-CERRO DEL AIRE
  • CTRA.PLANTÍO-NOVOTIENDAS
  • CTRA.PLANTÍO-LOS SAUCES
  • MARTÍN PESCADOR-AV.VICTORIA
  • CTRA.PLANTÍO-CLUB DE TENIS
  • AV.VICTORIA-AV.ESTACIÓN
  • AV.VICTORIA-CALVO SOTELO
  • AV.VICTORIA-CIMARRA
  • AV.VICTORIA-SAIZ DE LA CALLEJA
  • AV.VICTORIA-VIRGEN DE LOS OLMOS
  • AV.VICTORIA-OCHANDIANO
  • AV.PADRE HUIDOBRO-PºERMITA
  • ARAQUIL-ARANDILLA
  • AV.OSA MAYOR-ARÁNDIGA
  • LEOPOLDO CALVO SOTELO-HNOS.FDEZ.CARVAJAL
  • AV.JUAN XXIII-COLEGIOS
  • AV.JUAN XXIII-SEVERO MªAGUSTÍN
  • AV.JUAN PABLO II-PORTUGALETE
  • AV.JUAN PABLO II-PATONES
  • SAGUNTO-CIRILO PALOMO
  • TENERÍAS-AV.HUERTA GRANDE
  • ANTONIO DÍAZ-EST.POZUELO
  • CTRA.HÚMERA-ELENA APARICIO
  • RAMÓN Y CAJAL-CTRA.HÚMERA
  • CIRILO PALOMO-CHINCHÓN
  • AV.JUAN PABLO II-AV.VALDENIGRALES
  • AV.JUAN PABLO II-PZA.ESPAÑA
  • AV.JUAN PABLO II-MÁRTIRES OBLATOS
  • ALMANSA-ARAGÓN
  • RAMÓN Y CAJAL-CTRA.HÚMERA
  • CTRA.HÚMERA-ELENA APARICIO
  • PZA.ESTACIÓN-EST.POZUELO
  • AV.JUAN XXIII-COLEGIOS
  • LEOPOLDO CALVO SOTELO-CASTILLO
  • AV.OSA MAYOR-ARÁNDIGA
  • PICOS DE EUROPA-POL.IND.SAN FERNANDO
  • SAN BLAS-URB.CASABLANCA
  • PZA.JAIME MERIC-CRISTO
  • MAGDALENA-PZA.CANTO REDONDO
  • SOLANO-AQUILÓN
  • GTA.RÍO ZÁNCARA-CTRA.HÚMERA
  • GABRIEL GªMÁRQUEZ-ANTONIO FDEZ.MARÍA
  • PLAYA DE LOURO-CHOPOS
  • PLAYA DE LOURO-ISLAS CIES
  • ISLA DE LA TOJA-PLAYA DE LOURO
  • AV.LAS SUERTES-AV.SIETE PICOS
  • REAL-POLICIA LOCAL
  • REAL-PZA.ESPAÑA
  • REAL-ZOCO
  • CTRA.LA GRANJA-GUARDIA CIVIL
  • MATALPINO-INSTITUTO
  • CTRA.MORALZARZAL-EL ROBLE
  • LIBERTAD-VILLA CARLOTA
  • DR.JOSÉ MªPOVEDA-EL RASO
  • DR.JOSÉ MªPOVEDA-URB.LA CERCA
  • CONCEJO-URB.CASABLANCA
  • CTRA.M608-URB.LAS CAÑADAS
  • CTRA.M608-URB.EL SOTO
  • CTRA.M608-CEMENTERIO
  • CTRA.MORALZARZAL-COL.VIRGEN ENEBROS
  • CTRA.MORALZARZAL-EL ROBLE
  • MATALPINO-INSTITUTO
  • CTRA.LA GRANJA-GUARDIA CIVIL
  • REAL-ZOCO
  • ISLA DE LOBEIRA-PLAYA LA LANZADA
  • MAR DE FORA-PLAYA DE LOBEIRA
  • HONORIO LOZANO-IGLESIA
  • ALMENDROS-COLEGIO
  • AV.JUAN CARLOS I-PUENTE LOS DELFINES
  • CAMINO DE LA GUIJA-URB.ALHAMBRA
  • and 8156 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

23 findings, ordered by severity.

Show every finding
  • Error10 instances

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

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Error10 instances

    Stop time with arrival before previous departure time (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

  • Warning14230 instances

    14230 of 14230 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus 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)

  • Warning5952 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning5350 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning2442 instances

    2442 of 8406 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)

  • Warning1178 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning309 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning308 instances

    Between two distant stops, the times imply a speed no bus reaches.

    A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.

    Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)

    Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning139 instances

    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)

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

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning38 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning24 instances

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning2 instances

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    More than one entity (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: more_than_one_entity · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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)

  • 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Info8396 instances

    About 8396 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)

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

  • 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 · 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. 2 validator errors to resolve. States wheelchair access on 71% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
2 validator errors to resolve.
Current Met
Service data covers the next 355 days.
Accessible Not yet
States wheelchair access on 71% 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 5350 of 8397 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

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 355 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 20 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 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 40 / 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 Autobuses Urbanos (Madrid regional urban bus) GTFS data quality grade: F

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-red-de-urbanos/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.