GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

BAS.MY Alor Setar

Based on the feed this agency publishes

Service mode Bus

57.8 / 100

First scorecard for this agency

Catalogued in Kedah, Malaysia.

Covers 161 daysAccessibility gapsRealtime not yet published

The federally supported BAS.MY stage bus network serving Alor Setar and other parts of Kedah. A 2026-07-22 preflight found 14 routes, 804 trips, 393 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

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

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

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

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

Correctness67.5 / 100

The MobilityData validator flagged 6 kinds of issue across 592 instances (0 error, 590 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

  • 28 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("BINTANG MAYA / BANDAR PERDANA", "AMAN CENTRAL / MENARA ALOR SETAR", "MARDI/KG TELUK CHENGAI", 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.

  • K10 (red)
  • K20 (red)
  • K30 (red)
  • K40 (red)
  • K41 (red)
  • K50 (red)
  • K51 (red)
  • K52 (red)
  • K60 (red)
  • K61 (red)
  • K62 (red)
  • K63 (red)
  • K100(O) (red)
  • K100(I) (red)
Routes in BAS.MY Alor Setar's feed
RouteTypeLine color
K10 SHAHAB PERDANA - KUALA KEDAHBusred
K20 SHAHAB PERDANA - JITRABusred
K30 SHAHAB PERDANA - KUALA NERANGBusred
K40 SHAHAB PERDANA - PENDANG VIA SIMPANG EMPATBusred
K41 SHAHAB PERDANA - PENDANG VIA KOTA SARANG SEMUTBusred
K50 SHAHAB PERDANA - SUNGAI PETANIBusred
K51 SUNGAI PETANI - TANJUNG DAWAIBusred
K52 SUNGAI PETANI - PANTAI MERDEKABusred
K60 SUNGAI PETANI - TAMAN BANDAR BARUBusred
K61 SUNGAI PETANI - TAMAN KELISABusred
K62 SUNGAI PETANI - TAMAN RIA JAYA TAMAN BATIKBusred
K63 SUNGAI PETANI - BANDAR PERDANABusred
K100(O) K100 ALOR SETAR FEEDER(O)Busred
K100(I) K100 ALOR SETAR FEEDER(I)Busred

This feed has 393 stops.

List every stop
  • TAMAN SERI PUTRA
  • TERMINAL SHAHAB PERDANA
  • STESEN BAS JITRA
  • STESEN BAS KUALA NERANG
  • PERHENTIAN BAS PENDANG
  • STESEN BAS SG PETANI
  • TANJUNG DAWAI
  • PANTAI MERDEKA
  • KLINIK KESIHATAN SG LALANG
  • TAMAN RIA
  • MYDIN TAMAN BATIK
  • BINTANG MAYA / BANDAR PERDANA
  • SHAHAB PERDANA
  • MASJID AL RAHMAH
  • MEDAN SELERA TAMAN WIRA MERGONG
  • TAMAN WIRA
  • KG LUBUK PERINGGI
  • STOR JKR
  • GIAT MARA
  • HOSPITAL ALOR SETAR
  • KOMPLEKS SUKAN
  • STADIUM DARUL AMAN
  • STADIUM DARUL AMAN 2
  • BAKAR BATA
  • WISMA KANCUT
  • AMAN CENTRAL / MENARA ALOR SETAR
  • DATARAN ALOR SETAR
  • PEKAN RABU
  • SEBERANG PERAK
  • HIJAU KUNING
  • SJK(C) SIN MIN
  • SIMPANG KUALA
  • KLINIK KESIHATAN SIMPANG KUALA 1
  • KLINIK KESIHATAN SIMPANG KUALA 2
  • KLINIK KESIHATAN SIMPANG KUALA 3
  • TAMAN ORKID
  • SMK TUN SHARIFAH RODZIAH
  • KOMPLEKS PENYIARAN RTM
  • MASJID AS SALAM
  • SJK(C) PEI HWA
  • MARDI/KG TELUK CHENGAI
  • SK TELUK KECHAI
  • SMK TENGKU LAKSMANA
  • TAMAN KEMUDI/KG TELOK KECHAI
  • MASJID AL HUDA/PUSAT SUMBER KEMAS
  • TAMAN RESTU
  • BATAS PAIP
  • BATAS PAIP 2
  • TAMAN LAYAR FASA 4 & 3
  • MASJID TUNKU ABDUL RAHMAN PETRA / KLINIK KESIHATAN
  • FAMA
  • MEE ABBAS
  • SK HAJI ISMAIL / MASJID INDIA
  • JETI KUALA KEDAH
  • PEJABAT POS
  • PEKAN KUALA KEDAH
  • SJK(C) PUMPONG
  • KOLEJ POLY TECH MARA
  • KOMPLEKS BADMINTON
  • PEJABAT DAERAH
  • JPJ
  • PANTAI JOHOR
  • ALOR MERAH
  • PETRONAS ALOR MERAH
  • APARTMENT KCS
  • KEDAH MEDICAL CENTRE
  • KELAB ROYAL KEDAH
  • WISMA DARUL AMAN
  • PENJARA
  • SMK SULTANAH BAHIYAH
  • SM DATO SYED OMAR
  • MRTC
  • TAMAN PKNK 2
  • TAMAN PKNK
  • OPP STADIUM DARUL AMAN
  • WISMA PKNK
  • UKIR MALL
  • IPD KOTA SETAR
  • UTC ALOR SETAR
  • KTM ALOR SETAR
  • SK WAN SULAIMAN SIDDIQ
  • KG BERJAYA
  • SEKOLAH TUNKU ABDUL RAHMAN
  • ASRAMA POLYTECH MARA
  • MASJID AL HASANAH
  • TAMAN RAKYAT MERGONG
  • KG MEMPELAM
  • LOTUS MERGONG
  • PLAZA PERABOT CLASSY GLORY
  • TAMAN SELAYANG
  • SEKOLAH MENENGAH KEBANGSAAN AGAMA KEDAH
  • BSN PEKAN RABU
  • OPP IPD KOTA SETAR
  • TAMAN SELADANG
  • PEJABAT PENGHULU TITI GAJAH / TAMAN BERLIAN / TAMAN KANCIL
  • MASJID TENGKU INTAN SYAFINAZ
  • KG ALOR SENJAYA
  • SK TITI GAJAH
  • TAMAN DESA MUTIARA
  • LAPANGAN TERBANG SULTAN ABDUL HALIM
  • TITI GAJAH
  • SMA TITI BESI
  • BIRO TATA NEGARA
  • TUDM KEPALA BATAS
  • PEKAN KEPALA BATAS
  • TAMAN JALAI JAYA
  • KEM TOK JALAI
  • SMK TUNKU ANUM
  • KEM SULTAN ABDUL HALIM
  • SM SULTAN ABDUL HALIM
  • TNB TANJUNG SEPAH
  • POLIMAS
  • SMK JITRA
  • SK JITRA
  • PEKAN JITRA
  • MASJID JITRA
  • TAMAN DESA SINARAN
  • BERNAS
  • SMK SERI MAHAWANGSA
  • PEJABAT HUTAN DAERAH
  • BATU 1
  • SMK SULTANAH ASMA / MASJID DERGA
  • SEKOLAH RENDAH AN NAJAAH
  • SJK(C) KEE CHEE
  • MASJID AL BUKHARY
  • SK SULTANAH ASMA
  • TAMAN JAYA
  • TAMAN BAYU BARU
  • TAMAN PUSPA KENCANA
  • TAMAN PULAI JAYA
  • TAMAN SERI ASTANA
  • HOSPITAL SULTANAH BAHIYAH
  • SHELL JALAN LANGGAR
  • MASJID AL BADAR / TAMAN AWANA
  • TAMAN AMIRA
  • MASJID NURUL IHSAN / TAMAN SERI KOTA
  • KLINIK KESIHATAN LANGGAR
  • MAKAM DIRAJA LANGGAR
  • PEKAN LANGGAR
  • SJK(C) TAI CHONG
  • ESTET PADI PADANG LANGGAR
  • KG TANJUNG MUSANG
  • SENTAP / KILANG SCS
  • SIMPANG KEBUN 500 / TAMAN INDAH
  • SK JABI
  • BHP BATU 9
  • KILANG PAPAN BEST PRODUCT
  • BATU 11 / PASARAYA K CERIA POKOK SENA
  • JABATAN PENDAFTARAN NEGARA
  • SK POKOK SENA
  • KAMPUNG AMAN / PEKAN POKOK SENA
  • BALAI POLIS POKOK SENA
  • MASJID AR-RAUDAH
  • SENA SPORT / KILANG BESI
  • SM SAINS POKOK SENA
  • KOMPLEKS ISLAM DARUL ULUM
  • BUKIT LEREK
  • KG BUKIT LEREK 2
  • SIMPANG KUBU / BATU 16
  • PEJABAT FELCRA BUKIT TAMPOI
  • MAHAD TAHFIZ ABU BAKAR
  • SK BUKIT TAMPOI
  • RUMAH ORANG TUA-TUA BUKIT BETHEL
  • KG NAKO NAMBUA 1
  • KG NAKO NAMBUA 2
  • MASJID TENGKU SHARAFUDDIN BADLISHAH
  • KOLEJ MARA KUALA NERANG
  • TAMAN BELIMBING
  • SMK KUALA NERANG
  • KEMAS
  • SMK DATO SHEIKH AHMAD
  • PEJABAT PEKHIDMATAN VETERINAR DAERAH PADANG TERAP
  • PEKAN KUALA NERANG
  • CENTRAL SQUARE
  • BAKAR ARANG
  • MASJID ABU BAKAR AS SIDDIQ
  • SMK CHE TOM
  • LOTUS BAKAR ARANG
  • KAWASAN PERINDUSTRIAN BAKAR ARANG
  • SANSHIN
  • TAMAN SRI WANG
  • SK SRI WANG
  • TAMAN KELADI
  • MASJID TAMAN KELADI
  • TAMAN KELADI 2
  • SJK(T) TAMAN KELADI
  • SIN MIN SECONDARY SCHOOL
  • LEBUH PERDANA 1
  • LEBUH PERDANA 2
  • SIMPANG BINTANG MAYA
  • SIMPANG KUALA 2
  • SMK TEKNIK ALOR SETAR
  • HENTIAN KOMPLEKS WANTAS
  • LEBUHRAYA SELATAN
  • SK DATO WAN MOHAMAD SAMAN
  • TANDOP
  • TAMAN DESA KAMILAH
  • TAMAN BERSATU
  • TAMAN SIMPANG EMPAT
  • KG KEPALA PARIT DALAM
  • TAMAN MERPATI
  • SMK TOKAI
  • KLINIK DESA TOKAI
  • PEJABAT PENDIDIKAN DAERAH PENDANG
  • SIMPANG JELAI
  • SK KAMPUNG RAMBAI
  • MASJID HASANI KAMPUNG RAMBAI
  • KG ALOR BUNGA SENA
  • TANAH MERAH
  • KG BANGGOL BESI
  • SK TANAH MERAH
  • SMK TANAH MERAH
  • TAMAN AMAN SEJAHTERA
  • DARSVILLE PARK
  • SMA ISLAH
  • RUMAH TUN MAHATHIR
  • SK SUNGAI KOROK LAMA
  • SK JALAN PEGAWAI
  • MAKTAB MAHMUD
  • MAKTAB MAHMUD 2
  • AGROBAZAAR JLN GUNUNG PERAK
  • BHP TAMAN GUNUNG PERAK
  • SK HAJI HASSAN ITAM
  • SMA IHYA UL ULUM AD DINIAH
  • MASJID AT TAQWA
  • SK BULUH LIMA
  • PUSAT PERNIAGAAN KOTA JAYA / KOTA SARANG SEMUT
  • SJK(C) MIN SIN
  • JALAN PENDANG TANAH MERAH
  • SK BUKIT CHORAS
  • PEKAN KOBAH
  • SIMPANG KTM KOBAH
  • CALTEX PENDANG
  • SIMPANG BUKIT RAYA
  • TAMAN GEMILANG 2
  • JABATAN PENDAFTARAN NEGARA PENDANG
  • SMK PENDANG
  • SJK(C) YENG CHENG
  • PERHENTIAN BAS KOTA SARANG SEMUT
  • TAMAN MADU LEBAH / SK BUKIT BESAR
  • SMA NAHDZAH
  • KG TUALANG
  • SIMPANG TIGA SG DAUN
  • SK SIMPANG TIGA SG DAUN
  • KLINIK DESA SIMPANG TIGA
  • PONDOK POLIS SG LIMA LUAR
  • SK PADANG LUMAT
  • MASJID UBUDIAH
  • SMA TAUFIKIAH KHAIRIYAH AL HALIMIAH
  • SJK(C) PEI HWA
  • and 143 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

12 findings, ordered by severity.

Show every finding
  • Warning804 instances

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

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

  • Warning393 instances

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

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

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

  • 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

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

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

  • Info391 instances

    About 391 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. 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 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. 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 68 / 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 Alor Setar 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-alor-setar/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.