Feed status · checked 2026-07-19
BAS.MY Melaka
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Melaka, 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.
Checked for changes 5 hours ago; last changed 5 hours ago.
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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (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
678 of 678 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
569 of 569 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.
Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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.
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.
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 89 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
- Fare information is published using GTFS Fares v2.
- 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 69 instances (12 error, 57 warning, 0 informational).
Service data covers the next 89 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
16 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Opp Taman Sri Krubong/Goldsta", "Kampung Bandar Hilir/Jalan Imam Jh Mohd", "Durable Farm & Resort Bemban", 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.
Fares are applied to trips.
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.
- M100 (yellow)
- M101 (yellow)
- M10A (yellow)
- M10B (yellow)
- M11 (yellow)
- M12 (yellow)
- M13 (yellow)
- M14 (yellow)
- M15 (yellow)
- M16 (yellow)
- M17 (yellow)
- M20 (yellow)
- M20X (yellow)
- M21 (yellow)
- M21X (yellow)
- M22 (yellow)
- M23 (yellow)
- M23X (yellow)
- M30 (yellow)
- M31 (yellow)
- M32 (yellow)
- M33 (yellow)
| Route | Type | Line color |
|---|---|---|
| M100 Bandaraya Melaka Feeder | Bus | yellow |
| M101 Pasar Melaka Feeder | Bus | yellow |
| M10A Melaka Sentral - MITC | Bus | yellow |
| M10B Melaka Sentral - MITC - Via Jalan Pengkalan Batu & AEON Melaka | Bus | yellow |
| M11 Melaka Sentral - Bukit Katil / Taman Saujana Permai | Bus | yellow |
| M12 Melaka Sentral - Airport Batu Berendam / Angkasa Nuri | Bus | yellow |
| M13 Melaka Sentral - Taman Inang Sari | Bus | yellow |
| M14 Melaka Sentral - Bertam Ulu / Tanjung Minyak Perdana | Bus | yellow |
| M15 Melaka Sentral - Pulau Gadong | Bus | yellow |
| M16 Melaka Sentral - Paya Luboh | Bus | yellow |
| M17 Melaka Sentral - Tangga Batu | Bus | yellow |
| M20 Melaka Sentral - Tampin via Alor Gajah | Bus | yellow |
| M20X Terminal Alor Gajah Sentral - Melaka Sentral | Bus | yellow |
| M21 Melaka Sentral - Tampin via Alor Gajah Durian Tunggal | Bus | yellow |
| M21X Terminal Alor Gajah Sentral - Melaka Sentral - Durian Tunggal | Bus | yellow |
| M22 Melaka Sentral - Bandar Vendor / UniKL | Bus | yellow |
| M23 Melaka Sentral - Masjid Tanah / Pengkalan Balak | Bus | yellow |
| M23X Terminal Masjid Tanah Sentral - Melaka Sentral | Bus | yellow |
| M30 Melaka Sentral - Batang Melaka via Selandar | Bus | yellow |
| M31 Melaka Sentral - Batang Melaka via Tebong | Bus | yellow |
| M32 Melaka Sentral - Jasin | Bus | yellow |
| M33 Jasin - Taman Seri Asahan | Bus | yellow |
This feed has 678 stops.
List every stop
- Melaka Sentral
- Aeon Ayer Keroh
- Hospital Melaka
- Opp Hospital Melaka
- Sirim Melaka
- Opp Sirim Melaka
- Texas Instrument
- Opp Texas Instrument
- Kiara Apartment Taman Mutiara
- Opp Kiara Apartment Taman Mutiara
- Taman Mutiara Melaka
- Opp Taman Mutiara Melaka
- Taman Ara
- Opp Taman Ara
- SK Batu Berendam 2
- Opp SK Batu Berendam 2
- SK Batu Berendam 1
- Opp SK Batu Berendam 1
- Coconut Shake Batu Berendam
- Medan Selera batu Berendam
- SMK Tun Mahathir
- Opp SMK Tun Mahathir
- Taman Beringin Melaka
- Opp Taman Beringin Melaka
- Mango Float Royale
- Opp Mango Float Royale
- Taman Putat Indah
- Opp Taman Putat Indah
- Opp Tokong Yui Yang Keong
- Tokong Yui Yang Keong
- Kampung Baru Ayer Keroh
- Klinik Kesihatan Air Keroh
- Opp Mydin MITC
- Mydin MITC
- Wisma Negeri
- Opp Wisma Negeri
- MITC
- Opp Zoo Melaka
- Zoo Melaka
- Mini Malaysia
- Opp Mini Malaysia
- UTEM
- Taman Sin Hoe
- Taman Goodwood
- Perbadanan Perpustakaan Awam Melaka
- Taman Bahagia
- Pangsapuri Seri Siantan
- Kampung Bukit Baru Dalam
- Sekolah Tinggi St David
- Balai Polis Bukit Baru
- Jabatan Pendidikan Melaka Bukit Baru
- Opp Aeon Ayer Keroh
- Kompleks Mahkamah Melaka
- Opp Kompleks Mahkamah Melaka
- Opp Pantai Hospital Melaka
- Pantai Hospital Meaka
- Taman Baru Bukit Katil
- Opp Taman Baru Bukit Katil
- Opp Masjid Sayyidina Ali
- Masjid Sayyidina Ali
- Taman Merak
- Opp Taman Merak
- Opp JPJ Melaka
- JPJ Melaka
- Taman Puncak Bukit Katil
- Kolej Vokasional Melaka Tengah
- Kampung Desa Tersusun
- Ins. Lat. Perindustrian Bukit Katil
- SK Kg Tun Razak
- Opp SK Kg Tun Razakk
- Taman Bukit Katil Damai 2
- Opp Lotus Melaka
- Lotus Melaka
- Aeon Bandaraya Melaka
- Opp Aeon Bandaraya Melaka
- Wisma Air
- Plaza Hang Tuah 2
- Medan Selera Tun Ali
- Kampung Lapang Bachang
- Kampung Bakar Batu
- Taman Widuri
- Kampung Baroh
- Jalan Salmah Baba
- Masjid Ar-Razzaq
- Kampung Bachang Barat
- Taman Pasir Puteh
- Taman Bachang Baru 1
- Security Force
- Kampung Tengah 1
- Taman Bachang Baru 2
- Kampung Tengah 2
- Lapangan Terbang Antarabangsa Melaka
- Klinik Desa Batu Beremdam
- Opp Taman Datuk Tamby Chik Karim
- Taman Datuk Tamby Chik Karim
- Opp Taman Merdeka
- Taman Merdeka
- Opp Taman Merdeka Jaya
- Taman Merdeka Jaya
- Taman Angkasa Nuri
- Opp Taman Angkasa Nuri
- Opp Taman Angkasa Nuri 2
- Opp Taman Mekar
- Opp Taman Mas Merah
- Taman Mas Merah
- Airport Fire And Rescue
- Opp Airport Fire And Rescue
- Taman Seri Songket
- Opp Taman Seri Songket
- Taman Mekar
- Opp Smjk Tinggi Cina Melaka
- Smjk Tinggi Cina Melaka
- Opp Taman Malim Indah
- Taman Malim Indah
- Opp Balai Panjang
- Balai Panjang
- Malim Jaya
- Opp Malim Jaya
- Pasar Malim Jaya
- Opp Pasar Malim Jaya
- Perindustrian Malim Jaya
- Opp Perindustrian Malim Jaya
- Opp Taman Bertam Mutiara
- Taman Bertam Mutiara
- Pos Logistic
- Xepa - Soul Pattinson
- Aik Cheong Beverage
- Taman Teknologi Cheng
- Nsk Trade City (Melaka)
- Taman Sri Krubong/Goldsta
- Umw Toyota
- Taman Sri Krubong 2
- Masjid As Salam
- Kampung Tampoi
- Taman Perindustrian Krubong
- Lt Hardware
- Opp Lt Hardware
- Kampung Ladang Melaka
- Taman Krubong Indah
- Opp Taman Krubong Indah
- Taman 1 Krubong
- Opp Taman 1 Krubong
- Opp Jalan 1 Krubong Gate 2
- Jalan 1 Krubong Gate 2
- Opp Taman Krubong Perdana
- Taman Krubong Perdana
- Kedai Nasi Ayam Jalan Pantai
- Taman Inang Sari
- Opp Taman Teknologi Cheng
- Opp Taman Sri Krubong/Goldsta
- Opp Nsk Trade City (Melaka)
- Opp Taman Bertam Malim
- Taman Bertam Malim
- Opp SK Malim
- SK Malim
- SMK Malim
- Opp SMK Malim
- Opp Taman Cheng Utama
- Taman Cheng Utama
- Opp Kampung Cheng
- Kampung Cheng
- Opp Taman Cheng Permai
- Taman Cheng Permai
- Opp Gerai MBMB Taman Cheng Baru
- Gerai MBMB Taman Cheng Baru
- Taman Cheng Perdana
- Opp Taman Cheng Perdana
- Opp Rumah Seri Kenangan Taman Cheng
- Rumah Seri Kenangan Taman Cheng
- Opp Balai Raya Kampung Cheng
- Balai Raya Kampung Cheng
- Opp Taman Bertam Indah
- Taman Bertam Indah
- Bertam Ulu Batu 10
- Opp Bertam Ulu Batu 10
- Tanjung Minyak Perdana
- Plaza Hang Tuah 1
- SJK (C) Yok Bin
- Melaka International School
- Persatuan Low Melaka
- SMK Gajah Berang
- Jalan Ong Kim Wee
- SJK(T) Melaka (Kubu)
- Persatuan Badminton Melaka
- Balai Polis Tengkera
- Taman Siantan / Masjid Tengkera
- SMK (P) Methodist
- Kampong Sembilan
- SK Tengkera 1 & 2
- Warung Hajjah Robiah
- Kuih Keria Haji Jalil
- Kuih Keria Hajah Rahmah
- Oriental Melaka Straits Medical Centre
- Taman Melati
- Lagenda Condo
- Masjid Saad Ibni Abi Waqqas
- Kampung Tengah Melaka
- Taman Sri Gadong
- SK Klebang Besar
- Taman Pulau Gadong Jaya
- Simpang Lorong Pokok Manggis
- Rumah Awam 2 Pulau Gadong
- Taman Gadong Bahagia
- Kompleks Pertanian Pulau Gadong
- Taman Bertam Perdana 1
- Taman Bertam Perdana 2
- Taman Mayfair
- Taman Kenanga
- Kampung Pesaran Balik Buluk Klebang
- Pantai Klebang
- Opp Pantai Klebang
- Balai Polis Batang Tiga
- Taman Muhibbah
- Dhammacakka Buddist Vihara
- Smk Klebang
- Kampung Rambai Tengah
- Taman Rambai Tengah
- Masjid Al Falah
- Kampung Setulang Daing
- Rumah Awam Bukit Rambai
- Kampung Bukit Rambai
- Maahad Tahfiz Kasyfu Al Ulum
- Taman Rambai Mutiara
- Taman Rambai Mesra
- Kampung Paya Mengkuang Melaka
- Kampung Daya Wawasan
- MPKK Bukit Rambai
- Pejabat Mca Bukit Rambai
- Klinik Kesihatan Bukit Rambai
- SMK Bukit Rambai
- MJ Construction
- Paya Luboh 1
- Taman Pizza Idaman
- Paya Luboh 2
- Paya Luboh 3
- PPR Tangga Batu
- Opp Balai Polis Batang Tiga
- Marina Point
- Seri Bayan Condominium
- Zill Golden Village
- Taman Panjang Impian
- SJK(C) Ek Te
- Sekolah Tunas Bakti / Ocean Palm Condo
- Taman Spring Garden
- SK Lereh
- Kampung Tanjung Kling
- Surau Tengah
- Tanjung Kling
- Masjid Bilal Bin Rabah Tanjong Kling
- Kampung Kelongkong
- and 428 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
9 findings, ordered by severity.
Show every finding
- Error12 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning678 instances
678 of 678 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)
- Warning569 instances
569 of 569 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)
- Warning20 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)
- Warning18 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Validator rule: equal_shape_distance_same_coordinates · 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)
- 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. 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 89 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 89 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 12 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 60 / 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 52 / 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/basmy-melaka/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.