GTFS Scorecard
← All agencies

Feed status · checked 2026-09-05

Hyderabad Metro Rail

Based on the official feed source on file

Service mode Metro

85.5 / 100

First scorecard for this agency

Catalogued in Telangāna, India.

Covers 1214 daysAccessibility gapsRealtime not yet published

The three-line Hyderabad metro (Red, Green, Blue), published through Open Data Telangana and named in feed_info.txt as such. The archive is an OpenCity copy of that export because HMRL's own open-data page routes the download through a Google Form, the same arrangement already recorded for the TGSRTC bus feed. A 2026-09-01 preflight found service dated from 2026-07-03 to 2030-01-01; the scorecard measures that distant horizon rather than reading it as proof of maintenance. Counted as one feed record and distinct from the TGSRTC bus network.

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 1 hours ago; last changed 1 hours 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

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

705 of 705 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

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

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

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

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

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
705 of 705 stops don't say whether a wheelchair user can board there.
Next action
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.
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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

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

  3. Review the flagged fields and fill in the ones your riders would use. · 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 1214 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness95.5 / 100

The MobilityData validator flagged 2 kinds of issue across 4 instances (0 error, 1 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 1214 days.

Rider experience59.9 / 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.

2 accessibility depth signals

  • 101 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("MYP Arm B Combined Staircase & Escalator", "MYP Arm C Combined Staircase & Escalator", "MYP Arm D Combined Staircase & Escalator", 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.

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

  • C3_BLUE (teal)
  • C2_GREEN (green)
  • C1_RED (red)
Routes in Hyderabad Metro Rail's feed
RouteTypeLine color
C3_BLUE Nagole - Raidurg - Nagole - C3Subway / metroteal
C2_GREEN JBS Parade Ground - MG Bus Station - JBS Parade Ground - C2Subway / metrogreen
C1_RED Miyapur - LB Nagar - Miyapur - C1Subway / metrored
List every stop
  • Ameerpet
  • Ameerpet
  • Ameerpet
  • Ameerpet
  • Ameerpet
  • AME Arm A Lift
  • AME Arm A Combined Staircase & Escalator
  • AME Arm B Staircase
  • AME Arm B Escalator
  • AME Arm B Lift
  • AME Arm B Combined Staircase & Escalator
  • AME Arm C Staircase
  • AME Arm C Escalator
  • AME Arm C Lift
  • AME Arm C Combined Staircase & Escalator
  • AME Arm D Staircase
  • AME Arm D Escalator
  • AME Arm D Lift
  • AME Arm D Combined Staircase & Escalator
  • Assembly
  • Assembly
  • Assembly
  • ASM Arm A Staircase
  • ASM Arm B Staircase
  • ASM Arm B Escalator
  • ASM Arm D Combined Staircase & Escalator
  • ASM Arm E Staircase
  • ASM Arm E Lift
  • Begumpet
  • Begumpet
  • Begumpet
  • BEG Arm A Lift
  • BEG Arm A Combined Staircase & Escalator
  • BEG Arm B Staircase
  • BEG Arm B Escalator
  • BEG Arm B Lift
  • BEG Arm B Combined Staircase & Escalator
  • BEG Arm C Staircase
  • BEG Arm C Escalator
  • BEG Arm C Lift
  • BEG Arm C Combined Staircase & Escalator
  • BEG Arm D Staircase
  • BEG Arm D Escalator
  • BEG Arm D Lift
  • BEG Arm D Combined Staircase & Escalator
  • Balanagar
  • Balanagar
  • Balanagar
  • BLR Arm A Staircase
  • BLR Arm A Lift
  • BLR Arm B Staircase
  • BLR Arm B Escalator
  • BLR Arm C Staircase
  • BLR Arm C Lift
  • BLR Arm D Staircase
  • BLR Arm D Escalator
  • Bharat Nagar
  • Bharat Nagar
  • Bharat Nagar
  • BTN Arm A Combined Staircase & Escalator
  • BTN Arm B Staircase
  • BTN Arm B Lift
  • BTN Arm C Combined Staircase & Escalator
  • BTN Arm D Staircase
  • BTN Arm D Lift
  • Chikkadpally
  • Chikkadpally
  • Chikkadpally
  • CDP Arm A Staircase
  • CDP Arm A Escalator
  • CDP Arm A Lift
  • CDP Arm A Combined Staircase & Escalator
  • CDP Arm B Staircase
  • CDP Arm B Escalator
  • CDP Arm B Lift
  • CDP Arm B Combined Staircase & Escalator
  • CDP Arm C Staircase
  • CDP Arm C Escalator
  • CDP Arm C Lift
  • CDP Arm C Combined Staircase & Escalator
  • CDP Arm D Staircase
  • CDP Arm D Escalator
  • CDP Arm D Lift
  • CDP Arm D Combined Staircase & Escalator
  • Chaitanyapuri
  • Chaitanyapuri
  • Chaitanyapuri
  • CHP Arm A Staircase
  • CHP Arm A Lift
  • CHP Arm B Combined Staircase & Escalator
  • CHP Arm C Lift
  • CHP Arm C Combined Staircase & Escalator
  • CHP Arm D Staircase
  • Durgam Cheruvu
  • Durgam Cheruvu
  • Durgam Cheruvu
  • DGC Arm B Staircase
  • DGC Arm B Lift
  • DGC Arm C Staircase
  • DGC Arm C Lift
  • DGC Arm D Staircase
  • DGC Arm D Escalator
  • Dilsukh Nagar
  • Dilsukh Nagar
  • Dilsukh Nagar
  • DSN Arm A Staircase
  • DSN Arm B Lift
  • DSN Arm B Combined Staircase & Escalator
  • DSN Arm C Lift
  • DSN Arm C Combined Staircase & Escalator
  • DSN Arm D Staircase
  • Erragadda
  • Erragadda
  • Erragadda
  • ERA Arm A Staircase
  • ERA Arm A Escalator
  • ERA Arm A Lift
  • ERA Arm A Combined Staircase & Escalator
  • ERA Arm B Staircase
  • ERA Arm B Lift
  • ERA Arm C Staircase
  • ERA Arm C Lift
  • ERA Arm D Staircase
  • ERA Arm D Escalator
  • ESI Hospital
  • ESI Hospital
  • ESI Hospital
  • ESI Arm A Staircase
  • ESI Arm A Escalator
  • ESI Arm B Staircase
  • ESI Arm B Lift
  • ESI Arm C Staircase
  • ESI Arm C Lift
  • ESI Arm D Staircase
  • ESI Arm D Escalator
  • Gandhi Bhavan
  • Gandhi Bhavan
  • Gandhi Bhavan
  • GAB Arm A Staircase
  • GAB Arm B Lift
  • GAB Arm B Combined Staircase & Escalator
  • GAB Arm C Lift
  • GAB Arm C Combined Staircase & Escalator
  • GAB Arm D Staircase
  • Gandhi Hospital
  • Gandhi Hospital
  • Gandhi Hospital
  • GNH Arm A Staircase
  • GNH Arm A Escalator
  • GNH Arm A Lift
  • GNH Arm A Combined Staircase & Escalator
  • GNH Arm B Staircase
  • GNH Arm B Escalator
  • GNH Arm B Lift
  • GNH Arm B Combined Staircase & Escalator
  • GNH Arm C Staircase
  • GNH Arm C Escalator
  • GNH Arm C Lift
  • GNH Arm C Combined Staircase & Escalator
  • GNH Arm D Staircase
  • GNH Arm D Escalator
  • GNH Arm D Lift
  • GNH Arm D Combined Staircase & Escalator
  • Habsiguda
  • Habsiguda
  • Habsiguda
  • HSG Arm A Staircase
  • HSG Arm A Lift
  • HSG Arm B Staircase
  • HSG Arm B Escalator
  • HSG Arm C Staircase
  • HSG Arm C Escalator
  • HSG Arm D Staircase
  • HSG Arm D Lift
  • HITEC City
  • HITEC City
  • HITEC City
  • HTC Arm A Staircase
  • HTC Arm A Escalator
  • HTC Arm B Staircase
  • HTC Arm B Lift
  • HTC Arm C Staircase
  • HTC Arm D Lift
  • HTC Arm D Combined Staircase & Escalator
  • Erra Manzil
  • Erra Manzil
  • Erra Manzil
  • IRM Arm A Lift
  • IRM Arm A Staircase
  • IRM Arm B Staircase
  • IRM Arm B Escalator
  • IRM Arm C Staircase
  • IRM Arm C Escalator
  • IRM Arm D Staircase
  • IRM Arm D Lift
  • JBS Parade Ground
  • JBS Arm A Staircase
  • JBS Arm A Escalator
  • JBS Arm A Lift
  • JBS Arm A Combined Staircase & Escalator
  • JBS Arm B Staircase
  • JBS Arm B Escalator
  • JBS Arm B Lift
  • JBS Arm B Combined Staircase & Escalator
  • JBS Arm C Staircase
  • JBS Arm C Escalator
  • JBS Arm C Lift
  • JBS Arm C Combined Staircase & Escalator
  • JBS Arm D Staircase
  • JBS Arm D Escalator
  • JBS Arm D Lift
  • JBS Arm D Combined Staircase & Escalator
  • Jubilee Hills Checkpost
  • Jubilee Hills Checkpost
  • Jubilee Hills Checkpost
  • JCP Arm A Staircase
  • JCP Arm A Lift
  • JCP Arm B Staircase
  • JCP Arm B Escalator
  • JCP Arm C Staircase
  • JCP Arm C Lift
  • JCP Arm D Combined Staircase & Escalator
  • JNTU College
  • JNTU College
  • JNTU College
  • JNT Arm A Lift
  • JNT Arm A Combined Staircase & Escalator
  • JNT Arm B Staircase
  • JNT Arm C Lift
  • JNT Arm C Combined Staircase & Escalator
  • JNT Arm D Staircase
  • Road No 5 Jubilee Hills
  • Road No 5 Jubilee Hills
  • Road No 5 Jubilee Hills
  • JR5 Arm A Staircase
  • JR5 Arm A Escalator
  • JR5 Arm B Staircase
  • JR5 Arm B Lift
  • JR5 Arm C Staircase
  • JR5 Arm C Escalator
  • JR5 Arm D Staircase
  • JR5 Arm D Lift
  • Khairatabad
  • Khairatabad
  • Khairatabad
  • KHA Arm A Staircase
  • KHA Arm A Escalator
  • KHA Arm B Staircase
  • KHA Arm B Lift
  • KHA Arm C Lift
  • and 455 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

5 findings, ordered by severity.

Show every finding
  • Warning2820 instances

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

  • Warning705 instances

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

  • 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 · See MobilityData GTFS Validator rules

  • 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

  • Info3 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. 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 Met
Service data covers the next 1214 days.
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 1214 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 96 / 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 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.

Hyderabad Metro Rail GTFS data quality grade: B

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/hmrl-hyderabad-metro/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.