← All agencies

Feed status · checked 2026-10-17

BAS.MY Melaka

Based on the official feed source on file

Service mode Bus

63.9 / 100

unchanged since 2026-10-16

Cataloged in Melaka, Malaysia.

Covers 91 daysAccessibility gapsRealtime not yet published

Source feed: https://api.data.gov.my/gtfs-static/mybas-melaka

The BAS.MY Melaka stage bus network, a federally supported service operated by Causeway Link and published as open data on data.gov.my; 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.4, validator 8.0.1.

Checked for changes 35 minutes ago; last changed 35 minutes 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.

About this feed

BAS.MY Melaka’s published feed lists 22 bus routes, 569 scheduled trips and 678 stops. The published file last changed on 2026-10-17.

Top things to fix

Fix 01

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ 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

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.

Fixing this covers all 678 stops in the feed.

⏱ 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

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.

Fixing this covers all 569 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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.

  1. Fix 01

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

  3. Fix 03 · 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. 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 91 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

Correctness60.0 / 100

The MobilityData validator flagged 5 kinds of issue across 69 instances (12 error, 57 warning, 0 informational).

Freshness85.0 / 100

Service data covers the next 91 days.

Rider experience52.5 / 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 published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 22 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (M100, M101, M10A, M10B, M11, and more).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 16 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Taman Ind. Kecik & Sederhana Paya Datok", "Durable Farm & Resort Bemban", "Jongker Walk/Stadhuys", 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.

FaresFares v2

Fares are applied to trips.

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.

This feed has 678 stops.

Skip to route and stop data

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.

  • M100 (pink)
  • M101 (pink)
  • M10A (pink)
  • M10B (pink)
  • M11 (pink)
  • M12 (pink)
  • M13 (pink)
  • M14 (pink)
  • M15 (pink)
  • M16 (pink)
  • M17 (pink)
  • M20 (pink)
  • M20X (pink)
  • M21 (pink)
  • M21X (pink)
  • M22 (pink)
  • M23 (pink)
  • M23X (pink)
  • M30 (pink)
  • M31 (pink)
  • M32 (pink)
  • M33 (pink)
Routes in BAS.MY Melaka's feed
RouteTypeLine color
M100 Bandaraya Melaka FeederBuspink
M101 Pasar Melaka FeederBuspink
M10A Melaka Sentral - MITCBuspink
M10B Melaka Sentral - MITC - Via Jalan Pengkalan Batu & AEON MelakaBuspink
M11 Melaka Sentral - Bukit Katil / Taman Saujana PermaiBuspink
M12 Melaka Sentral - Airport Batu Berendam / Angkasa NuriBuspink
M13 Melaka Sentral - Taman Inang SariBuspink
M14 Melaka Sentral - Bertam Ulu / Tanjung Minyak PerdanaBuspink
M15 Melaka Sentral - Pulau GadongBuspink
M16 Melaka Sentral - Paya LubohBuspink
M17 Melaka Sentral - Tangga BatuBuspink
M20 Melaka Sentral - Tampin via Alor GajahBuspink
M20X Terminal Alor Gajah Sentral - Melaka SentralBuspink
M21 Melaka Sentral - Tampin via Alor Gajah Durian TunggalBuspink
M21X Terminal Alor Gajah Sentral - Melaka Sentral - Durian TunggalBuspink
M22 Melaka Sentral - Bandar Vendor / UniKLBuspink
M23 Melaka Sentral - Masjid Tanah / Pengkalan BalakBuspink
M23X Terminal Masjid Tanah Sentral - Melaka SentralBuspink
M30 Melaka Sentral - Batang Melaka via SelandarBuspink
M31 Melaka Sentral - Batang Melaka via TebongBuspink
M32 Melaka Sentral - JasinBuspink
M33 Jasin - Taman Seri AsahanBuspink
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

Overall score across the last 16 checks — unchanged since 2026-10-16.

2026-10-02: 63.92026-10-03: 63.92026-10-04: 63.92026-10-05: 63.92026-10-06: 63.92026-10-07: 63.92026-10-08: 63.92026-10-09: 63.92026-10-10: 63.92026-10-11: 63.92026-10-12: 63.92026-10-13: 63.92026-10-14: 63.92026-10-15: 63.92026-10-16: 63.92026-10-17: 63.9
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-10-0263.9 first check
2026-10-0363.9 no change
2026-10-0463.9 no change
2026-10-0563.9 no change
2026-10-0663.9 no change
2026-10-0763.9 no change
2026-10-0863.9 no change
2026-10-0963.9 no change
2026-10-1063.9 no change
2026-10-1163.9 no change
2026-10-1263.9 no change
2026-10-1363.9 no change
2026-10-1463.9 no change
2026-10-1563.9 no change
2026-10-1663.9 no change
2026-10-1763.9 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-10-171008b3b098792027-01-16Current rubric: see the trend above
2026-10-162276917c8e882027-01-15Current rubric: see the trend above
2026-10-1501574e4ac3cd2027-01-14Current rubric: see the trend above
2026-10-14bd4fe981949e2027-01-13Current rubric: see the trend above
2026-10-13cd28808a23672027-01-12Current rubric: see the trend above
2026-10-12b8d95b6880ab2027-01-11Current rubric: see the trend above
2026-10-110e0779e24b512027-01-10Current rubric: see the trend above
2026-10-10cca136446a3c2027-01-09Current rubric: see the trend above
2026-10-096c87445ce8582027-01-08Current rubric: see the trend above
2026-10-084a576b8ddb9b2027-01-07Current rubric: see the trend above
2026-10-079cda5a2388d52027-01-06Current rubric: see the trend above
2026-10-0656df37a21cc72027-01-05Current rubric: see the trend above

Showing the 12 most recent of 78 periods.

What changed in this feed

Overall grade and score held steady since 2026-10-16.

The feed file was re-published since 2026-10-16.

What changed inside the export

  • Service now runs through 2027-01-16 (was 2027-01-15).

Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

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

    Finding code: 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.)

    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)

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

    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)

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

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · 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.)

    Finding code: 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.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide for equal_shape_distance_same_coordinates · 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.)

    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

    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)

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

Part of the Malaysia portfolio: the same scorecards for every feed we track in that group, on one free page.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

BAS.MY Melaka: GTFS feed quality grade D, 63.9 of 100, checked 2026-10-17. GTFS 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-10-17.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-10-17. 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.