Call-prep brief · checked 2026-07-19
Keretapi Tanah Melayu (KTMB)
Grade F · 17.2 / 100
Unchanged since 2026-07-18.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
No longer reported since the last check (1 finding):
- Service data runs out in 1 day(s). (scorecard_feed_expiring_soon)
This compares feed state. It does not identify who made a change or why.
Top three things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Service data ended 0 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.
Effort: Usually one export setting; export on a schedule so it never lapses again.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
191 of 191 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Effort: A column in stops.txt; your scheduling software likely has it.
Ready to send to the agency
Hi Keretapi Tanah Melayu (KTMB) team, Service data ended 0 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/ktmb-national/
Key facts
- Feed URL
- https://api.data.gov.my/gtfs-static/ktmb
- Last checked
- 2026-07-19
- Service window
- Feed has expired. Last service date 2026-07-19.
- Location
- Malaysia
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.