Feed status · checked 2026-07-19
Rapid Kuantan
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Pahang, 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.
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
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
635 of 635 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
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
270 of 270 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
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.
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.
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.
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 255 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
The MobilityData validator flagged 5 kinds of issue across 978 instances (0 error, 877 warning, 101 informational).
Service data covers the next 255 days.
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.
1 accessibility depth signal
4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("PONDOK POLIS P/BADAK", "SUNGAI ISAP/TOYOYA", "KOMPLEKS TERUNTUM/IPD KUANTAN", and more).
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.
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 dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 100 (blue)
- 101 (blue)
- 102 (blue)
- 200 (blue)
- T201 (green)
- 300 (blue)
- 301 (blue)
- 302 (blue)
- 303 (blue)
- 400 (blue)
- 401 (blue)
- 402 (blue)
- 500 (blue)
- 600 (blue)
- 601 (blue)
- 603 (blue)
- 604 (blue)
| Route | Type | Line color |
|---|---|---|
| 100 Hentian Bandar-Gambang Resort | Bus | blue |
| 101 Hentian Bandar-Inderapura/Indera Sempurna | Bus | blue |
| 102 Hentian Bandar-Permatang Badak | Bus | blue |
| 200 Hentian Bandar-Teluk Cempedak | Bus | blue |
| T201 KUANTAN CITY LOOP | Bus | green |
| 300 Hentian Bandar-Taman Impian | Bus | blue |
| 301 Hentian Bandar-Bukit Sagu | Bus | blue |
| 302 Hentian Bandar-Indera Mahkota 1 | Bus | blue |
| 303 Hentian Bandar-Terminal Sentral Kuantan | Bus | blue |
| 400 Hentian Bandar-Pekan | Bus | blue |
| 401 Hentian Bandar-RTC Kuala Pahang | Bus | blue |
| 402 HENTIAN BANDAR ~ SMK SUNGAI SOI | Bus | blue |
| 500 Hentian Bandar-Sungai Lembing | Bus | blue |
| 600 Hentian Bandar-Balok Makmur (via Jln Beserah) | Bus | blue |
| 601 Hentian Bandar-Kolej Polisas | Bus | blue |
| 603 Hentian Bandar-Kolej PSDC | Bus | blue |
| 604 Balok Makmur-Cherating | Bus | blue |
This feed has 635 stops.
List every stop
- PASARAYA JAYA GADING
- KOLEJ SHAHPUTRA
- SEKOLAH SAINS SULTAN HJ. AHMAD SHAH
- PENJARA PENOR
- PLKN
- BALAI BOMBA INDERA MAHKOTA
- INDERA MAHKOTA 8
- KAMPUNG PANCHING
- RESTORAN RASA MESRA
- BATU 16
- DHAS
- LKPP
- TAMAN SRI MAULANA
- KOMPLEKS TERUNTUM/IPD KUANTAN
- JKR DAERAH KUANTAN
- DEWAN MAT KILAU
- TERUS MAJU
- KOLEJ MATRIKULASI GAMBANG
- KAMPUNG NADAK
- KLINIK KESIHATAN PERAMU JAYA
- SMK PAYA BESAR
- TAMAN SEPAKAT
- SMK TENGKU PANGLIMA PERANG
- SHELL PEKAN
- PERUMAHAN INDERAPURA
- KAMPUNG PADANG
- RANGKAIAN DELIMA
- TAMAN LKNP
- YAYASAN PAHANG
- PERUMAHAN TAMAN IMPIAN
- KAMPUNG BARU ATONG
- BATU 11
- UMP
- KAMPUNG BATU SAWAR
- KAMPUNG KOLEK
- PASARAYA GIANT
- KAMPUNG TIRAM
- KLINIK DESA PENOR
- LOT KEDAI AIR PUTIH
- TAMAN BUKIT GOH PERDANA
- JAYA GADING
- MENARA TM
- SERI MELATI
- KOMPLEKS PENYAYANG
- PASARAYA NIRWANA
- INDERA MAHKOTA 8
- P.A.K.R PANCHING
- ENG HONG
- PERUMAHAN RAKYAT
- KILANG VAC
- PLKN
- MAAHAD TAHFIZ
- PETRONAS TANJUNG LUMPUR
- GAMBANG RESORT
- SHELL BUKIT SETONGKOL
- KILANG VAC
- HOMEBOX DESIGN
- KOLEJ PROFESSIONAL MARA
- SMK DATO’MAHMUD MAT
- LOT KEDAI TG. LUMPUR
- TUNAS CAPITAL
- SK TANAH PUTEH
- KAMPUNG TIRAM
- SURAU BKT SETONGKOL
- (M) SUNGAI LEMBING
- WAWASAN AL HUDA
- KAMPUNG SUNGAI CHARU
- SIMPANG BUKIT KUIN 3
- PASARAYA JAYA GADING
- LRG CEMPAKA 2
- DEWAN SERBAGUNA
- PERUMAHAN PAYA TIGA
- LOT KEDAI IM 2
- TUNAS MANJA
- BALAI POLIS GAMBANG
- PEJABAT KEMAS
- JAYA GADING
- SUNGAI ISAP/TOYOYA
- KEDIAMAN UMP 3
- SIMPANG JLN TERATAI
- PASARAYA JAYA GADING
- (M) POLISAS
- FURINDO FUNITURE
- PERUMAHAN SEMAMBU 1
- KAMPUNG LAMIR
- TONG AH ESTATE
- BALAI BOMBA INDERA MAHKOTA
- KAMPUNG CEMPAKA AMAN
- (M) LORONG CEMPAKA 2
- SK SUNGAI LEMBING
- TUNAS MANJA
- KLINIK DESA PANCHING
- TANAH PUTIH BARU
- LOT KEDAI PAYA TIGA
- BHP GAMBANG
- PASARAYA JAYA GADING
- PEJABAT PELAJARAN DAERAH PEKAN
- LADANG TUNAS AGRO
- (M) SMK INDERA MAHKOTA 2
- PERUMAHAN SEMAMBU
- KAMPUNG KUALA KENAU
- TANGKI AIR
- PETRONAS PERAMU JAYA
- MASJID BUKIT SETONGKOL
- KOMERSIAL SUNGAI ISAP JAYA
- HOMEBOX DESIGN
- MC DONALD
- MASJID NEGERI PAHANG
- CALTEX GAMBANG
- CENDERAWASIH
- SK KG.PADANG JAYA
- MASJID LAMA
- BATU 12
- MASJID PEKAN
- BALAI POLIS
- TAMAN INDERAPURA
- KUARTERS PENJARA PENOR
- PERODUA
- KAMPUNG LAMIR
- KOMPLEKS PENYAYANG
- SIMPANG BUKIT KUIN 3
- PEJABAT KEMAS
- HUB PERMATANG BADAK
- TAMAN MENTIGA JAYA
- CALTEX
- LOT KEDAI TG. LUMPUR
- HOSPITAL TENGKU AMPUAN AFZAN
- PADANG MPK 2
- MASJID INDERA MAHKOTA
- PERKAMPUNGAN RASAU PERDANA
- JKR DAERAH KUANTAN
- SHELL JLN BESERAH
- LRG CEMPAKA 5
- PETRONAS DARAT MAKBAR
- BERKAT HARDWARE
- BATU 3
- KOLEJ KOMUNITI PEKAN
- BATU 9
- PERUMAHAN LKNP
- CRYSTAL CITY HOTEL
- CALTEX GAMBANG
- MAAHAD TAHFIZ
- KOLEJ PROFESSIONAL MARA
- (M) COWBOY JALAN HAJI AHMAD
- PANTAI SEPAT 1
- TAMAN INDERAPURA
- PUSAT RELA
- KAMPUNG CEMPAKA
- SEKOLAH SAINS SULTAN HJ. AHMAD SHAH
- KUANTAN PARADE
- LOJI AIR SG.LEMBING
- KOSPEK MPK
- KAMPUNG PADANG PERDANA
- KUARTERS KESIHATAN
- PANTAI SEPAT 1
- KAMPUNG PADANG
- SMK MAT KILAU
- UTC KUANTAN
- SHELL JLN SG. LEMBING
- GIAT MARA
- UOB BANK
- PERKAMPUNGAN RAZALI
- DEWAN MAT KILAU
- MEDAN SELERA
- SHELL BUKIT SETONGKOL
- SIMPANG KOLEJ MATRIKULASI
- PERUMAHAN IM 1
- (M) SMK SUNGAI SOI
- PERUMAHAN PAYA TIGA
- PERUMAHAN TAMAN IMPIAN
- LOJI AIR SG.LEMBING
- BALAI POLIS SG. LEMBING
- SMK AIR PUTIH
- TONG AH ESTATE
- SMK INDERA MAHKOTA 2
- PERUMAHAN INDERAPURA
- SIMPANG SUNGAI PANDAN
- SMK MAT KILAU
- PERODUA
- KLINIK KESIHATAN SG. LEMBING
- RESTORAN ZAM ZAM
- PANTAI SEPAT 2
- BKT SETONGKOL 1
- BAITUR RAHAH
- KAMPUNG BATU SAWAR
- KAMPUNG SERI DAMAI
- TUNAS MART
- SIMPANG KG. KAWAH
- KEDAI BUAH
- YAYASAN PAHANG
- KEMUNTING
- PERAMU MAJU
- KOLEJ KOMUNITI PEKAN
- SHELL BUKIT GOH
- (M) TELUK CEMPEDAK
- TANGKI AIR
- KAMPUNG PANCHING
- BKT SETONGKOL 1
- KAMPUNG CEMPAKA AMAN
- SMK SRI MAHKOTA
- KAMPUNG BATU PUTIH
- KAMPUNG SUNGAI DERHAKA
- SK SUNGAI LEMBING
- PADANG BOLA
- (M) TUNAS MART BATU 11
- (M) MAJLIS BANDARAYA KUANTAN
- MEDAN SELERA
- TABUNG HAJI
- (M) TAMAN IMPIAN
- SHAHPUTRA VILLAGE
- MASJID PEKAN
- SK PANCHING
- SK GALING
- KUARTERS SKM
- ENG HONG
- MASJID AL-HIDAYAH PERMATANG BADAK
- ISUZU
- IBU PEJABAT POLIS KONTINJEN PAHANG
- BATU 8
- PENJARA PENOR
- KAMPUNG KOLEK
- DIN MOTOR
- TAMAN BELUKAR MAJU
- PETRONAS DARAT MAKBAR
- SK PANCHING
- BERKAT HARDWARE
- KEDAI BUAH
- PEJABAT POS
- BHP GAMBANG
- (M) PASARAYA TERUS MAJU
- KAMPUNG HIJRAH
- MENARA TM
- (M) CRYSTAL CITY HOTEL
- PASIR KEMUDI
- RESTORAN ZAMAN
- KLINIK KESIHATAN SG. LEMBING
- MABIQ
- SK GALING
- BALAI POLIS
- TANAH PUTIH
- SIMPANG SUNGAI PANDAN
- LRG CEMPAKA 1
- SM PENDIDIKAN KHAS VOKASIONAL
- MABIQ
- PEKAN PANCHING
- SMK TENGKU PANGLIMA PERANG
- (M) KAMPUNG UBAI
- (M) SK BATU 3
- KAMPUNG PAK MAHAT
- KEDIAMAN UMP 2
- and 385 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 58.8 | first check |
| 2026-07-19 | 58.8 | 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.
The feed file was re-published since 2026-07-18.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Warning781 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)
- Warning635 instances
635 of 635 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)
- Warning270 instances
270 of 270 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning84 instances
84 of 270 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus 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)
- Warning79 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.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning16 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.)
Validator rule: stop_too_far_from_shape · 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
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)
- Info631 instances
About 631 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)
- Info101 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · 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).
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. 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 255 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 255 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 73 / 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 18 / 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/rapidkuantan-bus/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.