Feed status · checked 2026-09-13
BAS.MY Kota Bharu
Based on the official feed source on file
Service mode Bus
up 7.9 since 2026-09-12 · F → F
Catalogued in Kelantan, 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.3, validator 8.0.1.
Checked for changes 33 hours ago; last changed 33 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
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 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
346 of 346 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
132 of 132 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
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
- Stop time with arrival before previous departure time (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- 346 of 346 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
- Feed evidence
- 132 of 132 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' 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 for scorecard_wheelchair_boarding_unknown
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_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 for scorecard_wheelchair_accessible_unknown
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 in 109 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 336 instances (6 error, 328 warning, 2 informational).
Service data covers the next 109 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
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("KLINIK DR AZIZ", "JALAN BAYAM 1 / KPJ PERDANA", "KK PERIA / CHUCOH PUTERI").
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.
This feed has 346 stops.
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.
- D51 (red)
- D52 (red)
- D60 (red)
- D61 (red)
- D62 (red)
| Route | Type | Line color |
|---|---|---|
| D51 KOTA BHARU - JERTEH VIA PASIR PUTEH | Bus | red |
| D52 KOTA BHARU - KAMPUNG RAJA VIA TOK BALI | Bus | red |
| D60 KOTA BHARU - KUALA KRAI VIA MACHANG | Bus | red |
| D61 KOTA BHARU - UITM MACHANG | Bus | red |
| D62 KOTA BHARU - GUA MUSANG | Bus | red |
List every stop
- KEDAI UNIFI KELANTAN
- STESEN BAS KOTA BHARU
- NAGOYA
- KELANTAN STATE MUSEUM
- SK PADANG GARONG
- PADANG GARONG
- BAZAR TOK GURU
- PEJABAT POS KOTA BHARU
- RESIDENSI TROIKA
- KB MALL
- KEDIAMAN IMIGRESEN
- PEJABAT PERIKANAN
- JKR NEGERI KELANTAN
- PETRONAS JALAN KUALA KRAI
- BATU 2
- KG BUNUT PAYONG 1
- KG BUNUT PAYONG 2
- BATU 3
- WISMA SERI NILAM WAKAF CHE YEH
- WAKAF CHE YEH
- CABANG PASIR HOR
- MASJID SULTAN ISMAIL PETRA
- KFC PASIR TUMBOH
- KOLEJ JURURAWAT JLN DUSUN MUDA
- JERTEH
- MASJID ULUL ALBAB SEBERANG JERTEH
- KG PADANG LUAS
- KK PADANG LUAS
- MASJID AS SOLIHIN
- SK PADANG LUAS
- KG PADANG LANDAK
- KLINIK DESA PADANG LANDAK
- MASJID KG LAK LOK
- KG LAK LOK
- SMUA NURUL HUDA
- MASJID IBRAHIM WAKAF RAJA
- KG WAKAF RAJA
- MASJID HAJI CHIK
- WAKAF LICHONG
- MASJID WAKAF LICHONG
- KG BUKIT BELAH
- KK GAAL
- KG GAAL 2
- KG GAAL 1
- SMK LONG GAFFAR
- SMK LONG GAFFAR 2
- WAKAF SIKU
- LIMBAT
- SK LANGGAR
- TAMAN MAJU 1
- TAMAN MAJU 2
- TAMAN HUDA
- KBMC
- MASJID AR RAHMAN
- YOUNG HARDWARE
- SK PERINGAT
- MASJID AT TAUHID PERINGAT
- PERINGAT
- TAMAN DESA PERINGAT
- KG BECHAH KURA
- KG MACHANG BUBUK
- KG WAKAF TOK WALI
- SK PADANG KALA
- KG PADANG KALA
- MASJID IMANUL FAIZIN
- KG KUBANG TIN
- MASJID AL MAGHFIRAH
- SMK MELOR
- MELOR 1
- SMUA AZHARIAH
- KK MAHLIGAI
- MASJID MAHLIGAI
- MASJID KG PAK BADOL
- SMK PAK BADOL
- KG TENGAH
- KG JERUS
- KG DANAN
- KLINIK ASSALAM
- BALAI ISLAM
- LEMBAGA PERTUBUHAN PELADANG
- PASAR SEGAR KK
- KG BUKIT TANAH
- MASJID BUKIT TANAH
- TAMAN DESA ATIRA
- BALAI POLIS SELISING
- KG SELISING
- PASAR SITI SARAH
- KG BANIR BELIKONG
- KK BUKIT ABAL
- SK BUKIT ABAL
- KG SG KELONG
- ISTANA KELANTAN
- KK PADANG PAK MAT
- MASJID PADANG PAK AMAT
- SK PADANG PAKMAT
- KG CHICHA
- PASARAYA PKT PASIR PUTEH
- KLINIK DR AZIZ
- PKT PASIR TUMBOH
- SRI AMAN DALAM
- MASJID AL MAJIDIAH
- SMK TOK JANGGUT
- BALAI BOMBA PASIR PUTEH
- MARA PASIR PUTEH
- PEJABAT TANAH DAN GALIAN PASIR PUTEH
- SK PASIR PUTEH
- PEKAN PASIR PUTEH
- PASAR JELAWAT
- JALAN NARA PASIR PUTEH
- BANDAR BARU JELAWAT
- MASJID IBRAHIMI PASIR PUTEH
- KG RUSA
- PASIR PUTEH SENTRAL
- SMK DATO PERDANA
- MAAHAD SANIAH
- PEJABAT PENDIDIKAN DAERAH BACHOK
- MASJID AL BALAGHUL MUBIN
- SK SERI AMAN PASIR PUTEH
- WAKAF BUNUT
- SK GAAL
- CHABANG MELAWI
- STADIUM SULTAN MUHAMMAD IV
- JALAN BAYAM 1 / KPJ PERDANA
- WISMA PERSEKUTUAN
- JALAN BAYAM 2
- SK SULTAN ISMAIL 2
- TAMAN MAJU
- POLITEKNIK BESUT
- STESEN BAS KUALA KRAI
- PUSAT ISLAM UITM MACHANG
- HENTIAN GUA MUSANG
- SIMPANG PERINGAT - BACHOK
- KG PADANG MOKKAN
- SK PADANG MOKKAN
- GIAT MARA PRIMA MELOR
- KG BADAK MATI
- MASJID PAUH LIMA
- KEDAI PAUH LIMA
- KG TEPUS
- MASJID TEPUS
- BALAI POLIS GUNONG
- KK GUNONG
- SMK SRI GUNUNG
- BUKIT BATOR
- HOSPITAL BACHOK
- BATOR
- SMK JELAWAT
- MASJID AR RAHMAN REPEK
- KG REPEK
- PUSAT PEMULIHAN OKU TELONG
- KG TELONG
- MASJID AL TARBIYAH AL ISLAMIYAH
- PUSAT PENGAJIAN PONDOK KANDIS
- SIMPANG KK KANDIS
- MYDIN TUNJUNG
- G ORANGE MALL
- PERTUBUHAN PELADANG KANDIS
- KG KANDIS
- JABATAN PENDIDIKAN NEGERI KELANTAN
- KG AIR TAWAR
- TUNJUNG
- MASJID MUKIM TUNJUNG
- SHELL TOK BALI
- CHERANG RUKU
- KG DALAM RHU
- KLINIK DESA DALAM RHU
- SK DALAM RHU
- KG PACHAKAN
- BHP KUALA BESUT
- PASARAYA PKT TUNJUNG
- KK KUALA BESUT
- KG GERTAK SERATUS
- KEDAI MULONG 1
- SMK KUALA BESUT
- SK KUALA BESUT
- KEDAI MULONG 2
- MASJID AL FALAH
- NILAM PURI
- MASJID BATU 8
- KG BERANGAN
- KADA KADOK
- TERMINAL BAS KUALA BESUT
- MASJID KADOK
- PUSAT KHIDMAT DUN KADOK
- PASAR NELAYAN SEBERANG KASTAM
- KG AIR TAWAR BESUT
- JPJ BESUT
- KG PENGKALAN NYIREH
- MASJID IBNU ABBAS PENGKALAN NYIREH
- PETRON KG RAJA
- KK KG RAJA
- PEJABAT TANAH DAN DAERAH BESUT
- MASJID NASIRUDDIN SHAH KG RAJA
- INSTITUTE MEMANDU BESUT
- SMK PEMAISURI NUR ZAHIRAH
- MRSM KOTA PUTERA
- IPG SULTAN MIZAN
- PINTU MASUK POLITEKNIK BESUT
- ASRAMA
- HENTIAN BAS EKSPRES KUALA KRAI
- DESKOH
- KOLEJ VOKASIONAL KUALA KERAI
- DAMAR
- MRSM Kuala Krai
- HOSPITAL SULTAN ISMAIL PETRA KUALA KRAI
- KK PAHI
- SMK PAHI
- MASJID MUKIM PAHI
- SK PERIA
- SIMPANG PERIA
- KK PERIA / CHUCOH PUTERI
- SIMPANG CHUCOH PUTERI
- MASJID LEPAN JENUT
- KG TANJUNG BATU MANIK URAI
- MANIK URAI LAMA 2
- MANIK URAI BARU
- PASAR MANIK URAI BARU
- LALOH
- SK LELA JASA
- SIMPANG SG SAM
- SG BAYU
- PONDOK SG BAYU
- LADANG SERASA
- PEJABAT OPERASI KESEDAR PALOH
- PALOH
- CHIKU 3
- CHIKU 2
- CHIKU 1
- SUNGAI ASAP
- RENOK BARU
- KTM GUA MUSANG
- STESEN BAS GUA MUSANG
- HOSPITAL GUA MUSANG
- SMK KADOK
- KG KADOK
- BATU 10 LORONG HJ MUSTAFAR
- BATU 11 JLN PENGKALAN BUT
- MASJID BATU 11
- TALI AIR BATU 11
- BOMBA KETEREH
- PEJABAT POS KETEREH
- KEDAI KETEREH
- STESEN BAS KETEREH
- CABANG TOK AKIL
- SMK KETEREH
- KG DENDANG
- TERMINAL BAS EKSPRES KOK LANAS
- KOK LANAS
- KK KOK LANAS
- ECONJAYA KOK LANAS
- and 96 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 7.9 since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 58.7 | first check |
| 2026-08-07 | 58.7 | no change |
| 2026-09-12 | 49.1 | down 9.6 |
| 2026-09-13 | 57.0 | up 7.9 |
What changed since your last check
- Correctness up 18.0
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-09-13 the grade held, though the score fell from 59 to 57. As of 2026-09-13 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-09-13 Score rose 8 points, correctness rose 18 points.
- 2026-09-12 Score fell 10 points, correctness fell 22 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error6 instances
Stop time with arrival before previous departure time (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning346 instances
346 of 346 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning326 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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning132 instances
132 of 132 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info344 instances
About 344 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.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 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.)
Finding code: unknown_column · Read the fix guide for unknown_column · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. 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 Met
- Service data covers the next 109 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 107 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 6 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 66 / 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.
Part of the Malaysia portfolio: the same scorecards for every feed we track in that group, on one free page.
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/basmy-kota-bharu/2026-09-13.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-13. 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.