Feed status · checked 2026-07-19
Keretapi Tanah Melayu (KTMB)
Based on the feed this agency publishes
Service mode Tram + Rail
unchanged since 2026-07-18
Catalogued in Malaysia.
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.
Checked for changes 4 hours ago; last changed 6 hours ago.
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
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
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.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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.
⏱ Varies.worth about +12 points in its category
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
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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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. See this feed's finding-clearance log.
Review the rule documentation for 'foreign_key_violation' 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.
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. 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 today.
- 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
- 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 11 kinds of issue across 524 instances (2 error, 522 warning, 0 informational).
Service data ended 0 day(s) ago. Trip planners have likely already dropped this feed.
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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| Padang Besar Line KTM Butterworth - Padang Besar | Tram / light rail | green (no shape in feed) |
| Ipoh Line KTM Butterworth - Ipoh | Tram / light rail | teal (no shape in feed) |
| ERT Intercity Ekspres Rakyat Timuran Tumpat - JB Sentral | Rail | purple (no shape in feed) |
| ES Intercity Ekspres Selatan Gemas - JB Sentral | Rail | purple (no shape in feed) |
| ETS Electric Train Service Padang Besar - Gemas | Rail | purple (no shape in feed) |
| Port Klang Line KTM Tanjung Malim - Pelabuhan Klang | Tram / light rail | red (no shape in feed) |
| Seremban Line KTM Batu Caves - Pulau Sebang/Tampin | Tram / light rail | teal (no shape in feed) |
| SH Intercity Shuttle Tumpat - Gemas | Rail | purple (no shape in feed) |
| ST Intercity Shuttle Tebrau JB Sentral - Woodlands | Rail | purple (no shape in feed) |
This feed has 191 stops.
List every stop
- BUTTERWORTH
- SIMPANG AMPAT
- KOTA BHARU (PK)
- KAMPAR
- TAPAH ROAD
- SUNGKAI
- SLIM RIVER
- BEHRANG
- TANJUNG MALIM
- KALUMPANG
- KUALA KUBU BARU
- RASA
- BATANG KALI
- Nibong Tebal
- Serendah
- RAWANG
- KUANG
- Kepong Sentral
- SUNGAI BULUH
- KEPONG
- Segambut
- Putra
- Bank Negara
- PARIT BUNTAR
- KUALA LUMPUR
- KL SENTRAL
- Midvalley
- Seputih
- SALAK SELATAN
- BANDAR TASEK (S)
- SERDANG
- KAJANG
- KAJANG 2
- UKM
- BANGI
- BATANG BENAR
- Nilai
- LABU
- Tiroi
- SEREMBAN
- Senawang
- SUNGAI GADUT
- Rembau
- Pulau Sebang (Tampin)
- BAGAN SERAI
- Batang Melaka
- Gemas
- Batu Anam
- Segamat
- Genuang
- TENANG
- Labis
- Bekok
- Paloh
- Chamek
- BUKIT MERAH
- Kluang
- Mengkibol
- Rengam
- Layang-Layang
- SEDENAK
- Kulai
- SENAI
- Skudai
- Kempas Bahru
- Pasir gudang
- HOLIDAY PLAZA
- DANGA CITY MALL
- JB SENTRAL
- Woodlands
- Gelang Patah
- Tanjung Pelepas
- BUKIT TENGAH
- TASEK GELUGOR
- SUNGAI PETANI
- GURUN
- Kobah
- TOKAI
- Alor Star
- ANAK BUKIT
- Kodiang
- KAMUNTING
- KODIANG
- ARAU
- BUKIT KATRI
- Taiping
- PADANG BESAR
- SENTUL
- Batu Kentonmen
- Kampung Batu
- Taman Wahyu
- BATU CAVES
- ABDULLAH HUKUM
- Angkasapuri
- Pantai Dalam
- PETALING
- Jalan Templer
- Kg.Datuk Harun
- Seri Setia
- SETIA JAYA
- SUBANG JAYA
- BATU TIGA
- SHAH ALAM
- PADANG JAWA
- Bukit Badak
- KLANG
- Teluk Pulai
- Teluk Gadong
- Kampung Raja Uda
- JALAN KASTAM
- PEL. KLANG (S)
- PULAU INDAH
- PADANG RENGAS
- BUKIT MERTAJAM
- LONDAH
- ROMPIN
- Bahau
- SERTING
- Kuala Kangsar
- Kemayan
- Mengkuang
- Triang
- MENTRI
- Mengkarak
- Mentakab
- Kerdau
- SUNGAI DALAM
- Kuala Krau
- Jenderak
- JERANSONG
- Jerantut
- PADANG PIOL
- TEMBELING
- Mela
- SUNGAI LIK
- Krambit
- KUALA LIPIS
- Pdg.Tungku
- KG TELANG
- B.Betong
- Kg.Berkam
- Dura
- Aur Gading
- SUNGAI SIPUT
- Chegar Perah
- Sungai Temau
- KUBANG RUSA
- Teluk Gunong
- Merapoh
- Mentara Baru
- LAPAN TUPAI
- Gua Musang
- Pan Malayan
- Sungai Koyan
- Kampung Sg.Sirian
- Sungai Sirian
- Limau Kasturi
- Bertam Baru
- Bertam
- Jerek Baru
- Sungai Tasin
- Sri Bintang
- Sri Mahligai
- Sri Jaya
- Kemubu
- Dabong
- Kuala Gris
- CHEMOR
- Bukit Abu
- Kg Baru Bukit Abu
- Ulu Temiang
- Kg.Baru Sg.Mengkuang
- Manek Urai
- Pahi
- Kuala Krai
- Sungai Nal
- Temangan
- Tanah Merah
- Bukit Panau
- Sungai Keladi
- To' Uban
- Cicha Tinggi
- Pasir Mas
- Bunut Susu
- Wakaf Bahru
- TASEK
- Kampung Kok Pasir
- TUMPAT
- IPOH
- LAHAT
- BATU GAJAH
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 17.2 | first check |
| 2026-07-19 | 17.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
New since 2026-07-18 (1 finding)
- Error1 instance
Service data ended 0 day(s) ago.
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
No longer reported since 2026-07-18 (1 finding)
- Service data runs out in 1 day(s). (scorecard_feed_expiring_soon)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-18 this feed started at grade F. On 2026-07-19 feed expired. On 2026-07-19 the check no longer reported: service data runs out in 1 day(s). As of 2026-07-19 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-19 Feed expired.
Everything we checked
19 findings, ordered by severity.
Show every finding
- Error2 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
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.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning304 instances
304 of 304 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning304 instances
304 of 304 trips have no headsign.
Riders at the stop can't tell which direction a transit vehicle is going.
Fix: Populate trip_headsign to match what the transit vehicle displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning191 instances
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.
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 (opens the GTFS Schedule reference on an external site)
- Warning171 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning112 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning89 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Validator rule: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning89 instances
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unused_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning47 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 (opens the validator rules on an external site)
- Warning8 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle 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.)
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
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 (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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info84 instances
About 84 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 (opens GTFS Best Practices on an external site)
- 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 (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 0 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 0 days ago.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 89 of 304 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
- 8 of 191 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 2 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 28 / 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 0 / 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 16 / 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/ktmb-national/2026-07-19.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-19. 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.