GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Rapid Rail KL (LRT, MRT and monorail)

Based on the feed this agency publishes

Service mode Tram + Metro

59.6 / 100

unchanged since 2026-07-18

Catalogued in Wilayah Persekutuan Kuala Lumpur, Malaysia.

Covers 165 daysAccessibility gapsRealtime not yet published

Prasarana's Klang Valley urban rail: the LRT Ampang, Sri Petaling and Kelana Jaya lines, the MRT Kajang and Putrajaya lines, and the KL Monorail. Its primary Kuala Lumpur location is not a service boundary; the network also serves Selangor. A distinct published feed from the Rapid Bus networks, counted as one feed 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

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

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

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

Fix 03

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 (the file itself is absent) 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

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

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

Correctness71.2 / 100

The MobilityData validator flagged 7 kinds of issue across 152 instances (0 error, 142 warning, 10 informational).

Freshness85.0 / 100

Service data covers the next 165 days.

Rider experience23.1 / 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 not published.

Accessibility0 / 100

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

2 accessibility depth signals

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (AGL, PYL, MRL, SAL).

    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.

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("TAMAN TUN DR ISMAIL").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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.

  • AGL (orange)
  • BRT (green)
  • KGL (green)
  • KJL (red)
  • MRL (yellow)
  • SPL (brown)
  • PYL (yellow)
  • SAL (pink)
Routes in Rapid Rail KL (LRT, MRT and monorail)'s feed
RouteTypeLine color
AGL LRT Ampang LineSubway / metroorange
BRT BRT Sunway LineTram / light railgreen
KGL MRT Kajang LineSubway / metrogreen
KJL LRT Kelana Jaya LineSubway / metrored
MRL KL Monorail LineSubway / metroyellow
SPL LRT Sri Petaling LineSubway / metrobrown
PYL MRT Putrajaya LineSubway / metroyellow
SAL LRT Shah Alam LineSubway / metropink

This feed has 187 stops.

List every stop
  • SENTUL TIMUR
  • PUDU
  • CHAN SOW LIN
  • MIHARJA
  • MALURI
  • PANDAN JAYA
  • PANDAN INDAH
  • CEMPAKA
  • CAHAYA
  • AMPANG
  • SENTUL
  • TITIWANGSA
  • PWTC
  • SULTAN ISMAIL
  • BANDARAYA - UOB
  • MASJID JAMEK
  • PLAZA RAKYAT
  • HANG TUAH
  • SUNWAY-SETIA JAYA
  • MENTARI
  • SUNWAY LAGOON
  • SUNMED
  • SunU-Monash
  • SOUTH QUAY-USJ 1
  • USJ7
  • KWASA DAMANSARA
  • KWASA SENTRAL
  • KOTA DAMANSARA
  • SURIAN
  • MUTIARA DAMANSARA
  • BANDAR UTAMA
  • TAMAN TUN DR ISMAIL
  • PHILEO DAMANSARA
  • PUSAT BANDAR DAMANSARA
  • SEMANTAN
  • MUZIUM NEGARA
  • PASAR SENI
  • MERDEKA
  • BUKIT BINTANG
  • TUN RAZAK EXCHANGE
  • COCHRANE
  • MALURI
  • TAMAN PERTAMA
  • TAMAN MIDAH
  • TAMAN MUTIARA
  • TAMAN CONNAUGHT
  • TAMAN SUNTEX
  • SRI RAYA
  • BANDAR TUN HUSSEIN ONN
  • BATU 11 CHERAS
  • BUKIT DUKUNG
  • SUNGAI JERNIH
  • STADIUM KAJANG
  • KAJANG
  • GOMBAK
  • KLCC
  • KAMPUNG BARU - CBP COOPBANK PERTAMA
  • DANG WANGI
  • MASJID JAMEK
  • PASAR SENI
  • KL SENTRAL - REDONE
  • BANGSAR - BANK RAKYAT
  • ABDULLAH HUKUM
  • KERINCHI
  • UNIVERSITI
  • TAMAN MELATI
  • TAMAN JAYA
  • ASIA JAYA
  • TAMAN PARAMOUNT
  • TAMAN BAHAGIA
  • KELANA JAYA
  • LEMBAH SUBANG
  • ARA DAMANSARA
  • GLENMARIE
  • SUBANG JAYA
  • SS 15
  • WANGSA MAJU
  • SS 18
  • USJ 7
  • TAIPAN
  • WAWASAN
  • USJ 21
  • ALAM MEGAH
  • SUBANG ALAM
  • PUTRA HEIGHTS
  • SRI RAMPAI
  • SETIAWANGSA
  • JELATEK
  • DATO' KERAMAT
  • DAMAI
  • AMPANG PARK
  • KL SENTRAL
  • CHOW KIT
  • TITIWANGSA
  • TUN SAMBANTHAN
  • MAHARAJALELA
  • HANG TUAH
  • IMBI
  • BUKIT BINTANG
  • RAJA CHULAN
  • BUKIT NANAS
  • MEDAN TUANKU
  • KWASA DAMANSARA
  • KAMPUNG SELAMAT
  • SUNGAI BULOH
  • DAMANSARA DAMAI
  • SRI DAMANSARA BARAT
  • SRI DAMANSARA SENTRAL
  • SRI DAMANSARA TIMUR
  • METRO PRIMA
  • KEPONG BARU
  • JINJANG
  • SRI DELIMA
  • KAMPUNG BATU
  • KENTOMEN
  • JALAN IPOH
  • SENTUL BARAT
  • TITIWANGSA
  • HOSPITAL KUALA LUMPUR
  • RAJA UDA
  • AMPANG PARK
  • PERSIARAN KLCC
  • CONLAY
  • TUN RAZAK EXCHANGE
  • CHAN SOW LIN
  • KUCHAI
  • TAMAN NAGA EMAS
  • SUNGAI BESI
  • SERDANG RAYA UTARA
  • SERDANG RAYA SELATAN
  • SERDANG JAYA
  • UPM
  • TAMAN EQUINE
  • PUTRA PERMAI
  • 16 SIERRA
  • CYBERJAYA UTARA
  • CYBERJAYA CITY CENTRE
  • PUTRAJAYA SENTRAL
  • BANDAR UTAMA
  • STADIUM SHAH ALAM
  • DATO' MENTERI - SA SENTRAL
  • UITM SHAH ALAM
  • SEKSYEN 7
  • BANDAR BARU KLANG
  • PASAR KLANG
  • JALAN MERU
  • KAYU ARA
  • JAMBATAN KOTA
  • TAMAN SELATAN
  • SERI ANDALAS
  • KLANG JAYA
  • BANDAR BUKIT TINGGI
  • JOHAN SETIA
  • BANDAR UTAMA 11
  • DAMANSARA IDAMAN
  • SUBANG
  • GLENMARIE 2
  • KERJAYA
  • SENTUL TIMUR
  • PUDU
  • CHAN SOW LIN
  • CHERAS
  • SALAK SELATAN
  • BANDAR TUN RAZAK
  • BANDAR TASIK SELATAN
  • SUNGAI BESI
  • BUKIT JALIL
  • SRI PETALING
  • AWAN BESAR
  • SENTUL
  • MUHIBBAH
  • ALAM SUTERA
  • KINRARA
  • IOI PUCHONG JAYA
  • PUSAT BANDAR PUCHONG
  • TAMAN PERINDUSTRIAN PUCHONG
  • BANDAR PUTERI
  • PUCHONG PERDANA
  • PUCHONG PRIMA
  • TITIWANGSA
  • PUTRA HEIGHTS
  • PWTC
  • SULTAN ISMAIL
  • BANDARAYA - UOB
  • MASJID JAMEK
  • PLAZA RAKYAT
  • HANG TUAH

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 59.62026-07-19: 59.6
Show the numbers
CheckScoreChange
2026-07-1859.6 first check
2026-07-1959.6 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.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

13 findings, ordered by severity.

Show every finding
  • Warning187 instances

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

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

  • Warning48 instances

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

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

    Validator rule: expired_calendar · 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

    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

  • Warning1 instance

    Some route colors don't contrast with their text color.

    Route badges get hard to read, most of all for riders with low vision.

    Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

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

  • Warning1 instance

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

    Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • 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

  • 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

  • Info180 instances

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

  • Info10 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Validator rule: unknown_column · 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 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 165 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 165 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 23 / 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.

Rapid Rail KL (LRT, MRT and monorail) 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/rapidkl-rail/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.