GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

BAS.MY Kota Bharu

Based on the feed this agency publishes

Service mode Bus

58.7 / 100

First scorecard for this agency

Catalogued in Kelantan, Malaysia.

Covers 161 daysAccessibility gapsRealtime not yet published

The federally supported BAS.MY stage bus network based in Kota Bharu and serving Kelantan. A 2026-07-22 preflight found 16 routes, 752 trips, 755 stops, and service through 2026-12-31; 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

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

Fix 02

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

755 of 755 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 03

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

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

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. 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. Self-check a feed before you publish.

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

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

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

Correctness69.5 / 100

The MobilityData validator flagged 4 kinds of issue across 743 instances (6 error, 735 warning, 2 informational).

Freshness85.0 / 100

Service data covers the next 161 days.

Rider experience22.6 / 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.

1 accessibility depth signal

  • 8 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("WISMA KDRM / ROYAL THAI CONSULATE GENERAL", "KELANTAN POLO & RIDING CLUB", "SMKA FALAHIAN / PASIR PEKAN", 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.

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.

  • D10 (red)
  • D11 (red)
  • D12 (red)
  • D13 (red)
  • D20 (red)
  • D21 (red)
  • D30 (red)
  • D31 (red)
  • D32 (red)
  • D40 (red)
  • D50 (red)
  • D51 (red)
  • D52 (red)
  • D60 (red)
  • D61 (red)
  • D62 (red)
Routes in BAS.MY Kota Bharu's feed
RouteTypeLine color
D10 KOTA BHARU - PENGKALAN CHEPABusred
D11 KOTA BHARU - SABAK VIA KEMUMINBusred
D12 KOTA BHARU - SABAK VIA LAPANGAN TERBANGBusred
D13 KOTA BHARU - PANTAI CAHAYA BULANBusred
D20 KOTA BHARU - PENGKALAN KUBOR VIA CHABANG EMPATBusred
D21 KOTA BHARU - PENGKALAN KUBOR VIA TUMPATBusred
D30 KOTA BHARU - PASIR MAS VIA SALORBusred
D31 KOTA BHARU - MERANTIBusred
D32 KOTA BHARU - RANTAU PANJANGBusred
D40 KOTA BHARU - JELI VIA TANAH MERAHBusred
D50 KOTA BHARU - BACHOK VIA BUKIT MARAKBusred
D51 KOTA BHARU - JERTEH VIA PASIR PUTEHBusred
D52 KOTA BHARU - KAMPUNG RAJA VIA TOK BALIBusred
D60 KOTA BHARU - KUALA KRAI VIA MACHANGBusred
D61 KOTA BHARU - UITM MACHANGBusred
D62 KOTA BHARU - GUA MUSANGBusred

This feed has 755 stops.

List every stop
  • KEDAI UNIFI KELANTAN
  • STESEN BAS KOTA BHARU
  • TAMAN KEMUMIN PENGKALAN CHEPA
  • NAGOYA
  • KELANTAN STATE MUSEUM
  • SK PADANG GARONG
  • PADANG GARONG
  • WISMA KDRM / ROYAL THAI CONSULATE GENERAL
  • MAAHAD MUHAMMADI LELAKI
  • KLINIK DARULNAIM
  • TANJUNG MAS
  • TAMAN UDA MURNI
  • KG GAYONG PENGKALAN CHEPA
  • KFC PENGKALAN CHEPA DRIVE THRU
  • SASABELL BEAUTY HQ
  • FOOD VILLAGE RESTAURANT
  • LORONG MASJID AL KAROMAH
  • KG BAUNG
  • SHELL KG BAUNG
  • PASAR TOK GURU
  • CHABANG TIGA
  • SMK PENGKALAN CHEPA
  • IPG KOTA BHARU
  • JALAN PADANG GOLF
  • TAMAN KURNIA JAYA 1
  • TAMAN KURNIA JAYA 2
  • SMS TENGKU MUHAMMAD FARIS PETRA
  • SMK PENGKALAN CHEPA 2
  • MRSM PENGKALAN CHEPA
  • IPD KOTA BHARU
  • MASJID TOK HAJI YAHYA
  • TAMAN DESA KEMUMIN
  • TAMAN BINARAYA
  • TAMAN MEMORIAL
  • KAWASAN PERINDUSTRIAN PENGKALAN CHEPA
  • AMANAH SAHAM NASIONAL BERHAD
  • DATARAN CHENG HO
  • SHELL JALAN KEBUN SULTAN
  • SMK KOTA BHARU
  • RESTORAN SATAY MALAYSIA
  • TANJUNG MAS 2
  • SRA TENGKU AMALIN AISHAH PUTRI
  • KG PENGKALAN TOK KASIM
  • SK SERI CHEMPAKA
  • KG RAMBUTAN RENDANG
  • KG CHEMPAKA
  • KG BERIS LANJUT
  • WISMA SINAR
  • KG BERIS LANJUT 2
  • KEBUN NUR IMAN
  • PANJI
  • KG PANCHOR
  • KG KEMUMIN
  • SMK KEMUMIN
  • KLINIK DESA KEMUMIN
  • RESTORAN DSARI AIRPORT
  • KELANTAN POLO & RIDING CLUB
  • TEBING TINGGI
  • SABAK COFFEE HOUSE
  • PANDAMART KOTA BHARU
  • MASJID RITHAUDEEN WAKAF MEK ZAINAB
  • TAMAN PERBANDARAN TENGKU ANIS
  • SMK TANJUNG MAS
  • KOLEJ TEKNOLOGI DARULNAIM
  • PERNAMA PENGKALAN CHEPA
  • LAPANGAN TERBANG SULTAN ISMAIL PETRA
  • TAMAN SERI PENGKALAN CHEPA
  • CAAM KOTA BHARU
  • PEJABAT PENGGAWA DAERAH KEMUMIN
  • KG TOK KAYA
  • SK PARANG PUTING
  • TELUK KITANG
  • AGRO BAZAAR KEDAI RAKYART
  • TEBING TINGGI 2
  • PANTAI CAHAYA BULAN
  • MAAHAD MUHAMMADI PEREMPUAN
  • MASJID MUHAMMADI
  • SMJK CHUNG HWA
  • GOK KAPOR
  • SK PENAMBANG
  • SMK PENAMBANG
  • KG TIKAT
  • SULTAN ISMAIL PETRA MOSQUE
  • AZRA INN
  • KG KIJANG
  • MASJID AL AMIN KG KIJANG
  • KG BADANG
  • MASJID AL MUNIR KG BADANG
  • SK CIK DERIS
  • KK BADANG
  • PANTAI TIMOR PCB
  • MARISSA BATIK
  • SK SEMUT API
  • BAZAR TOK GURU
  • PEJABAT POS KOTA BHARU
  • RESIDENSI TROIKA
  • KB MALL
  • ONE BUTTON SOLUTION SDN BHD
  • HOMESTAY KBCC KOTA BHARU
  • PETRONAS PASIR PEKAN
  • SK PASIR PEKAN
  • SMKA FALAHIAN / PASIR PEKAN
  • SHELL WAKAF BHARU
  • PEJABAT POS WAKAF BHARU
  • WAKAF BHARU
  • SK WAKAF BHARU
  • KG BELUKAR WAKAF BHARU
  • TAMAN KASTURI
  • SK KUBANG BATANG
  • KG KUBANG BATANG
  • PETRON CHABANG EMPAT
  • SK TARBIYAH
  • SMK CHABANG EMPAT
  • KG PASIR PUTEH
  • KG KUBANG PANJANG
  • KG TELAGA BATA
  • SK BUNOHAN
  • KG JUBAKAR
  • KG BAROH KOK PAUH
  • KG PAUH SEBANJAR
  • SK SRI NETING
  • SHELL NETING
  • MASJID AS-SOMADI
  • KG KETIL
  • PEJABAT POS PENGKALAN KUBOR
  • SK PENGKALAN KUBOR
  • PENGKALAN KUBOR
  • MADRASAH KG PALOH LUAR
  • MASJID AL AMANIAH
  • MASJID AZIZ AL HADI
  • SK BERANGAN 1
  • MAAHAD MUHAMMADI
  • WAT PHIKULTHONG
  • KK TUMPAT
  • KTM TUMPAT
  • SK SERI TUMPAT 1
  • SK SRI TUMPAT 2
  • KG JUBAKAR PANTAI
  • SK SG TAPANG
  • SENANGIN RESORT
  • GIATMARA TUMPAT
  • SMK GETING
  • 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
  • RTM
  • SK SERI KOTA
  • PANTAI TIMOR SERI KOTA
  • KG KOTA 1
  • KG KOTA 2
  • KEDAI RUNCIT MUWARA
  • KG GAUNG
  • KG PENDEK
  • SK PENDEK
  • MASJID PENDEK
  • KK PENDEK
  • DARUL NISWAH DUN SALOR
  • MASJID KAMAL HASSAN
  • KG CHABANG TIGA PENDEK
  • KG TELUK KANDIS
  • MASJID NURUL HUDA
  • KG GERTAK LEMBU
  • MADRASAH POHON SAGU
  • KG JERULONG
  • SMK SALOR
  • PONDOK POLIS SALOR
  • MASJID MAHMUD
  • KG DATO’
  • KG PARIT CINA
  • MB GUESTHOUSE
  • KG GUA
  • KG BARU 1
  • KG BARU 2
  • MADRASAH AS SAADAH
  • KG SEBERANG PASIR MAS
  • PETRON SALOR
  • PETRONAS PASIR MAS
  • JPN PASIR MAS
  • SJKC YOK ENG
  • PASIR MAS
  • HENTIAN OPPOSITE SJKC YOK ENG
  • HENTIAN OPPOSITE JPN PASIR MAS
  • HENTIAN OPPOSITE PETRONAS PASIR MAS
  • KOMPLEKS MAHKAMAH PASIR MAS
  • TERMINAL BAS TASEK RAJA PASIR MAS
  • SMK MAHMUD MAHYIDIN
  • KG BARU LUAR
  • HIOK LEE
  • LORONG KUBUR
  • SK KUTAN
  • KG KUTAN 1
  • KG KUTAN 2
  • SMUA AL ULUM
  • KG TENDONG
  • BALAI POLIS TENDONG
  • SMK TENDONG
  • SK OTHMAN TALIB
  • KG BECHAH / JALAN CHEMPAKA
  • KG BECHAH / JALAN MELOR
  • MASJID HUTAN CHENGAL
  • KOLEJ VOKASIONAL PASIR MAS
  • WISMA BONDA JALAN TENDONG
  • KG KAYU TINGGI 2
  • KG KAYU TINGGI 1
  • MASJID AL-TAQWA BUNUT SUSU
  • KTM BUNUT SUSU
  • KG BUNUT SUSU
  • KG BECHAH PALAS
  • KG BINJAL
  • MASJID AS SOLIHIN BECHAH SEMAK
  • KUBUR BECHAH SEMAK
  • SK PENGGU
  • KG TOK LIMIN
  • KG PAYA ULAR
  • KG PANGKAL KALA
  • SK PANGKAL KALA
  • KG APA APA
  • KG ALOR MENGKUANG
  • KG GELANG MAS 2
  • KG GELANG MAS
  • KG CHAT
  • MERANTI
  • SMK MERANTI
  • KK MERANTI
  • TAMAN KEBUN RAJA
  • KG BANGGOL PAK MAT 2
  • KG BANGGOL PAK MAT 1
  • MASJID BAKONG LUAR
  • KG CHABANG BAKONG
  • KK POHON TANJUNG
  • KG LUBUK KAWAH
  • MASJID KG LUBUK KAWAH
  • KG GEBENG
  • PAAN SEAFOOD
  • KG GAJAH MATI
  • KG BANGGOL PERDANA
  • KG BANGGOL ARA
  • SK BANGGOL CHICHA
  • BANGGOL CHICHA
  • MAHAAD TAHFIZ AL ASRIAH
  • SRI AL FURQAN
  • KG KUBANG BADAK
  • WISMA KODMAS
  • and 505 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

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

    Validator rule: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules

  • Warning755 instances

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

  • Warning752 instances

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

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

  • 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

    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

  • Info748 instances

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

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

    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. 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 161 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 161 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 70 / 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.

BAS.MY Kota Bharu 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/basmy-kota-bharu/2026-07-23.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-23. 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.