GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

BAS.MY Johor Bahru

Based on the feed this agency publishes

Service mode Bus

55.6 / 100

First scorecard for this agency

Catalogued in Johor, Malaysia.

Covers 89 daysAccessibility gapsRealtime not yet published

The BAS.MY Johor Bahru 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.2, validator 8.0.1.

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

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.

⏱ 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

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

1782 of 1782 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 '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.

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

Correctness42.0 / 100

The MobilityData validator flagged 7 kinds of issue across 330 instances (39 error, 291 warning, 0 informational).

Freshness85.0 / 100

Service data covers the next 89 days.

Rider experience51.2 / 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.

1 accessibility depth signal

  • 54 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Jalan Sierra Perdana 1/12", "Opp Blok 33 & 34", "MASJID KAMPUNG KANGKAR TEBRAU/SK KANGKAR", 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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • J100 (yellow)
  • J10 (yellow)
  • J11 (yellow)
  • J13 (yellow)
  • J15 (yellow)
  • J16 (yellow)
  • J200 (yellow)
  • J205 (yellow)
  • J20 (yellow)
  • J21 (yellow)
  • J22 (yellow)
  • J300 (yellow)
  • J30 (yellow)
  • J31 (yellow)
  • J32 (yellow)
  • J33 (yellow)
  • J34 (yellow)
  • J40 (yellow)
  • J42 (yellow)
  • J44 (yellow)
  • J50 (yellow)
Routes in BAS.MY Johor Bahru's feed
RouteTypeLine color
J100 JB Sentral KSL - JB SentralBusyellow
J10 JB Sentral - Terminal Bas Kota TinggiBusyellow
J11 JB Sentral - AEON Dato Onn via Setia IndahBusyellow
J13 JB Sentral - Larkin Sentral via MahmoodiahBusyellow
J15 JB Sentral - Mid Valley SouthkeyBusyellow
J16 B5 Johor Street Market / Plaza Angsana - Toppen TebrauBusyellow
J200 Terminal Masai PPR Seri Alam - Terminal MasaiBusyellow
J205 Terminal Bas Masai - Lotus Kota MasaiBusyellow
J20 JB Sentral - Terminal Bas MasaiBusyellow
J21 JB Sentral - Permas JayaBusyellow
J22 JB Sentral - Taman Scientex Pasir GudangBusyellow
J300 Terminal Kulai - Taman Putri KulaiBusyellow
J30 JB Sentral - Terminal KulaiBusyellow
J31 JB Sentral - Taman Pulai MutiaraBusyellow
J32 JB Sentral - Bandar Selesa JayaBusyellow
J33 JB Sentral - Taman Tan Sri YaacobBusyellow
J34 JB Sentral - Terminal Sutera MallBusyellow
J40 Larkin Sentral - Gelang Patah SentralBusyellow
J42 Terminal Gelang Patah - PendasBusyellow
J44 Larkin Sentral - Terminal Feri Puteri Harbour melalui AEON Bukit IndahBusyellow
J50 Larkin Sentral - PontianBusyellow

This feed has 987 stops.

List every stop
  • AEON Bukit Indah
  • Terminal Kulai
  • Terminal Pontian
  • Hab Sutera Mall
  • Terminal Gelang Patah
  • Opp SK TAMAN PERLING
  • SJK C Pei Hwa / Masjid Taman Perling
  • Opp Perling Apartment
  • Perling Apartment
  • Opp Caltex Taman Perling
  • Caltex Taman Perling
  • Opp Perling Heights
  • Ambank Bukit Indah
  • Opp AmBank Bukit Indah
  • Opp PERSIARAN INDAH (3)
  • PERSIARAN INDAH (3)
  • BUKIT INDAH 2
  • Opp BUKIT INDAH 2
  • Bus Stop Petron Bukit Indah
  • Opp Petron Bukit Indah
  • Indah Court Apartment
  • Opp Indah Court Apartment
  • Mcdonalds Taman Sutera
  • OPP Petron TUTA
  • Opp KFC TUTA /FARMASI PERENNIAL
  • Opp Shell TUTA
  • Opp TAN FURNITURE
  • TAN FURNITURE
  • Opp MCDONALDS TUN AMINAH / KEDAI BUAH
  • MCDONALDS TUN AMINAH / KEDAI BUAH
  • CALTEX TASEK CENTRAL
  • JALAN PENDEKAR 18
  • SEKOLAH AGAMA TUTA
  • OPP SEKOLAH AGAMA TUTA
  • SJK (T) TUTA
  • Opp 7 ELEVEN SRI ORKID
  • 7 ELEVEN SRI ORKID
  • Opp PERUMAHAN RAKYAT LIMA KEDAI
  • Opp Surau Nur Hidayah
  • JALAN BESTARI
  • OPP JALAN BESTARI
  • Opp Petronas Bkt Indah 1
  • Petronas Bkt Indah Persiaran Indah Utama
  • Opp Petronas Nusa Perintis
  • Opp CIMB GELANG PATAH
  • CIMB GELANG PATAH
  • SMK Gelang Patah
  • Opp SIMPANG JALAN INDAH 1/10
  • SIMPANG JALAN INDAH 1/10
  • Opp JALAN INDAH 1/14 - 1/20
  • JALAN INDAH 1/14 - 1/20
  • Opp PERSIARAN INDAH UTAMA
  • Opp Nusa Idaman
  • SK Taman Perling 3
  • Opp SK Taman Perling 3
  • Opp JALAN ISMAIL SULTAN
  • Petronas Bukit Indah
  • Opp Petronas Bukit Indah
  • Opp Surau Al Hidayah
  • Hutan Bandar MPJBT
  • Opp Rumah Rakyat Iskandar
  • Rumah Rakyat Iskandar
  • Opp BLOK 58
  • Restoran 777
  • Blok 33 & 34
  • Opp PERSATUAN PENGANUT BUDHA BAO LIAN SI
  • TERMINAL TUTA
  • Opp TERMINAL TUTA
  • Masjid Hjh. Mominbi Ahmad Angullia
  • Opp Restoran 777
  • Petron Pontian
  • Opp Petron Pontian
  • Econsave Pontian
  • OPP Taman Impian Indah
  • KAMPUNG SUNGAI BUNYI PARIT HAJI ISMAIL
  • OPP Taman Desa Molek
  • Kampung Parit Selangor
  • Kampung Selangor Baru
  • Bend Weld
  • Masjid Kampung Pengkalan Raja
  • Desa Sri Aman
  • GIATMARA TG Piai
  • Dewan Serbaguna Kg Parit Pasir Baru
  • HENTIAN BAS JALAN BESAR
  • Opp MAYBANK PEKAN NENAS
  • TAMAN PERINDUSTRIAN PEKAN NENAS 1
  • Taman Mewah
  • Hentian Jalan Besar
  • Opp Dewan Serbaguna Kg Parit Pasir Baru
  • Opp GIATMARA TG Piai
  • SK Pengkalan Raja
  • Opp Masjid Kampung Pengkalan Raja
  • OPP Bend Weld
  • OPP KAMPUNG PARIT BARU
  • OPP Kampung Parit Selangor
  • Opp KILANG JCS
  • OPP KAMPUNG SUNGAI BUNYI PARIT HAJI ISMA
  • Pangsapuri Sri Intan
  • Jalan Tasek 10
  • Jalan Tasek 15
  • Jalan Tasek 20
  • Jalan Tasek 24
  • Pangsapuri Sri Ilham
  • PPR Seri Alam
  • Opp Vista Seri Alam
  • Maybank Bandar Seri Alam
  • Dewanraya Bandar Seri Alam Jalan Suria
  • Jalan Suria 80
  • Opp SMK Dato Penggawa Timur
  • SMK Dato Penggawa Timur
  • Flat Balau Block G
  • Todays Market (Jalan Masai Lama)
  • Opp Selera Kampung Melayu
  • Selera Kampung Melayu
  • Persiaran Laksamana
  • BALAI POLIS GELANG PATAH
  • Jalan Dato Esa
  • Jalan Padi Mahsuri 11
  • Tune Hotel
  • Skudai Kanan
  • Kampong Pasir
  • Opp Bandar Baru Uda
  • Hentian Setia Indah
  • Bus Stop Petron Jalan Daya
  • SMK Taman Daya
  • Jalan Rumbia 39 2
  • Flat Jalan Nipah 11
  • Bus Stop Opp Shell Jalan Daya
  • Bus Stop TM Auto Tyre
  • Hankook Tyre
  • Opp Gerai Muafakat Johor
  • Bus Stop TNB Taman Daya
  • Taman Delima
  • Bus Stop SK Kangkar Tebrau
  • U turn Kangkar tebrau
  • Bus Stop Universal Cable
  • OPP Pasar Borong Pandan
  • OPP Petron Pandan
  • Shell Pandan
  • Jalan Bayu 11 (Caltex )
  • OPP Majidee
  • OPP KG Melayu Majidee
  • JALAN BAYU
  • OPP Restoran Aliff
  • Petron Pasir Gudang East
  • Mutiara Motors
  • Jalan Masai Lama 2
  • Sri Plentong
  • Hospital Columbia
  • Taman Ria Plentong
  • Taman Sentosa
  • OPP Caltex Taman Melodies
  • Pasir Pelangi
  • The Zone
  • OPP Crystal Crown
  • IPK Johor
  • Foon Yew High School
  • Opp Foon Yew High School
  • Opp The Zone
  • Opp IPK Johor
  • Flat Sri Stulang
  • Shell Taman Iskandar
  • OPP Plaza Pelangi
  • Opp Shell Taman Iskandar
  • Crystal Crown
  • Caltex Taman Melodies
  • Opp Petronas Bayu Puteri
  • OPP Taman Sentosa
  • Petronas Bayu Puteri
  • Opp RENAISSANCE
  • OPP Hospital Columbia
  • AEON (Side) Permas Jaya
  • OPP Mutiara Motors
  • Jalan Permas 7
  • Mon Glori
  • Restoran Aliff
  • SK Permas Jaya 3
  • KG Melayu Majidee
  • Majidee
  • Hub Permas Jaya
  • Jalan Permas 1/2
  • Pasar Borong Pandan
  • SK Permas Jaya 1
  • Poliklinik Rozikin
  • Opp Taman Bunga Ros
  • Kia Motors Plentong
  • Poliklinik Penawar Taman Istimewa
  • Petron TUTA
  • Opp Surau Hajjah Fatimah
  • Restoran Pokok Ceri
  • Skudai Parade
  • Kuarters PUB
  • UTM Skudai
  • Taman Teknologi
  • OPP Sepakat Jaya
  • OPP SK Senai
  • Hab Pekan Senai
  • OPP Pejabat LLM
  • OPP Caltex Saleng
  • OPP Petronas Saleng
  • OPP 7-Eleven Saleng
  • Pejabat Fama Negeri Johor
  • Kolej Vokasional ERT Azizah
  • OPP Hospital Kulai
  • Opp Apartment Larkin Indah
  • OPP Indahpura Iris Park
  • OPP Public Bank Kulai
  • Medan Selera Kulai
  • Arked Mara
  • Opp Jejantas Taman Sri Kulai
  • OPP Shell Kulai
  • Spg Jln Sengkang
  • Opp Taman Putri Persiaran Sri Putri 3(1)
  • Opp Flat Taman Putri
  • Taman Putri Kulai
  • SMK Kota Kulai
  • OPP SMK Kota Kulai
  • Flat Taman Putri
  • Taman Putri Persiaran Sri Putri 3(1)
  • Shell Kulai
  • Jejantas Taman Sri Kulai
  • SMK Munshi Abdullah Kulai
  • OPP Arked Mara
  • Public Bank Kulai
  • Indahpura Iris Park
  • Pertubuhan Peladang
  • Hospital Kulai
  • 7-Eleven Saleng
  • TJ Mart Saleng
  • Petronas Saleng
  • Kompleks Pekan Rabu
  • Caltex Saleng
  • Opp SK Kampung Pasir / Giant Tampoi
  • Pejabat LLM
  • BSN Senai
  • SK Senai
  • Sepakat Jaya
  • Opp Kuarters PUB
  • Shell Taman Puteri Skudai
  • Pejabat Pos Skudai
  • MBIP Skudai
  • TM Skudai
  • OPP Shell Bakawali
  • The Store Pandan
  • OPP Danga Bay
  • Opp Beletime / M-Suites
  • Opp IKEA Tebrau Jalan Tebrau
  • Dataran Bandaraya Johor Bahru / Sri Gela
  • Pusat Islam Negeri Johor
  • OPP Pusat Islam Negeri Johor
  • and 737 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
  • Error39 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

  • Warning1782 instances

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

  • Warning987 instances

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

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

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

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

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

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

  • 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

  • Info88 instances

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

  • 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 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 39 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 42 / 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 51 / 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 Johor Bahru 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-johor-bahru/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.