GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

BAS.MY Kuching

Based on the feed this agency publishes

Service mode Bus

47.4 / 100

First scorecard for this agency

Catalogued in Sarawak, Malaysia.

Covers 161 daysAccessibility gapsRealtime not yet published

The BAS.MY stage bus network based in Kuching, Sarawak. A 2026-07-22 preflight found 13 routes, 620 trips, 406 stops, and service through 2026-12-31; counted as one feed record.

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 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

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

620 of 620 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

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

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 161 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness43.5 / 100

The MobilityData validator flagged 7 kinds of issue across 7431 instances (6352 error, 1077 warning, 2 informational).

Freshness85.0 / 100

Service data covers the next 161 days.

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

  • 12 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("OPP BEDDING & CO", "ST ANN CHURCH", "SJKCH BATU 4 1/2", 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.

  • Q01 (red)
  • Q10 (red)
  • Q05 (red)
  • Q06 (red)
  • Q07 (red)
  • Q08 (red)
  • Q09 (red)
  • Q11 (red)
  • Q12 (red)
  • Q13 (red)
  • Q14 (red)
  • Q16 (red)
  • Q15 (red)
Routes in BAS.MY Kuching's feed
RouteTypeLine color
Q01 SAUJANA PARKING - TAMAN MALIHAHBusred
Q10 OPEN AIR MARKET - TERMINAL BAS SERIANBusred
Q05 SAUJANA PARKING - SMKA MATANG 2Busred
Q06 SAUJANA PARKING - KAMPUNG BENUKBusred
Q07 SAUJANA PARKING - SJK CHUNG HUA BATU KAWABusred
Q08 SAUJANA PARKING - TERMINAL BAS BAUBusred
Q09 OPEN AIR MARKET - MUARA TEBASBusred
Q11 SAUJANA PARKING - ARANG ROADBusred
Q12 SAUJANA PARKING - TAMAN HUI SINGBusred
Q13 OPEN AIR MARKET - SIBURANBusred
Q14 OPEN AIR MARKET - SUMMER MALLBusred
Q16 OPEN AIR MARKET - SUKMABusred
Q15 STUTONG BARU / KUCHING SENTRAL - SAUJANA PARKINGBusred

This feed has 406 stops.

List every stop
  • MATANG JAYA
  • TERMINAL SAUJANA PARKING
  • EMART MATANG
  • OPP BANGUNAN MARZUKI
  • PENDIDIKAN JALAN MATANG
  • COPAL SATOK
  • SEGO PRECINT 1
  • TAMAN SEJOLI
  • HERITAGE
  • AMBANK SATOK
  • BANGUNAN MARZUKI
  • TAMAN HUSSEIN
  • JALAN SEMARAK
  • TAMAN DAHLIA
  • JLN LAKSAMANA CHENG HO 3
  • BOULEVARD
  • JALAN DB MUSTAPHA
  • OPP BEDDING & CO
  • EVERISE BATU 4
  • THE BANQUET RESIDENCES
  • OPP KOMPLEKS BELIA SUKAN
  • SM SAINS
  • JLN TAZA (OPP SGH)
  • KEK LAPIS WARISAN
  • JLN TAZA (OPP BADARUDDIN)
  • TAMAN MALIHAH 3
  • JALAN NANAS BARAT
  • POH KWONG PARK
  • OPP LAVIZO
  • SUNNY HILL
  • OPP TIMBERLAND
  • LEVEL UP ROCK ROAD
  • OPP ROCK ROAD SEAFOOD
  • TM BATU LINTANG
  • SHELL BATU LINTANG
  • THE SPRING KUCHING
  • BANGUNAN SULTAN ISKANDAR
  • WATERFRONT 1
  • JALAN ABELL
  • KOLEJ KOMUNITI SANTUBONG
  • DEMAK LAUT INDUSTRIAL PARK
  • SEB SUBSTATION SEJINGKAT
  • SK PAJAR SEJINGKAT
  • SMK BAKO
  • KAMPUNG HIJRAH
  • PCC DEMAK
  • JALAN KWONG LEE BANK
  • OPP PETRON JLN PENDING
  • CHUNG HUA MIDDLE SCHOOL NO 1
  • OPP SUBARU KUCHING
  • OPP TOYOTA BORNEO MOBILITY
  • RIVERSIDE MAJESTIC HOTEL
  • HERITAGE GARDEN
  • SMK PETRAJAYA
  • JALAN MATANG 2
  • JALAN MATANG 3
  • JALAN MATANG 4
  • HENTIAN SMKA MATANG
  • POLITEKNIK KCH
  • FAMILY PARK
  • KPG MATANG LOT
  • BATU 9 - TAMAN SRI JAYA
  • KOLEJ VOKASIONAL MATANG
  • TAMAN SURIA JAYA
  • BATU 5 - TAMAN DAHLIA
  • KAMPUNG BENUK
  • KAMPUNG PUNAU
  • OPP SJKCH BATU 15
  • PULAPOL KCH
  • SEMENGGOH NATIONAL PARK
  • KAMPUNG SRI ARJUNA
  • ST ANN CHURCH
  • SJKCH BATU 10
  • MPP
  • KOTA SENTOSA
  • BORNEO HOUSE MUSEUM
  • EVERWIN KOTA SENTOSA
  • SK HARDWARE
  • SIMPANG SEMABA
  • SJKCH BATU 4 1/2
  • TIMBERLAND MEDICAL CENTRE
  • KOZI SQUARE
  • SGH
  • BADARUDDIN
  • TM JALAN WERE
  • ST TERESA
  • JALAN TAHO 1
  • OPP LORENZO
  • OPP INDIAN ASSOCIATION
  • ROCK ROAD SEAFOOD
  • OPP LEVEL UP ROCK ROAD
  • FARLEY KCH
  • OUM
  • JALAN PENRISSEN 2
  • KOTA PADAWAN 1
  • OPP SJKCH BATU 10
  • OPP ST ANN CHURCH
  • OPP RCBM HOSPITAL
  • JLN BORNEO HEIGHTS
  • BUNG BARAU
  • BALAI POLIS BADARUDDIN
  • OPP SJKCH NO 4
  • EVERBRIGHT PARK
  • EVERBRIGHT STATE
  • LAU FURNITURE
  • MJC BATU KAWA
  • TERMINAL BAS BAU
  • OPP SK ST STEPHEN
  • TAMAN INDAH
  • JALAN BAU - KUCHING 1
  • SJK CHUNG HUA PAKU
  • OPPOSITE SMK PAKU
  • TAMAN SINIAWAN
  • KAMPUNG KERANJI
  • OPP KPG BUNGA RAMPAI
  • KAMPUNG BUKIT PANCUR
  • SIMPANG BATU KITANG LAMA
  • BATU KITANG WATER TREATMENT PLANT
  • KAMPUNG BUMBOK
  • SIMPANG KAMPUNG TEMATU
  • SRBCH BATU 8 1/2
  • SIMPANG KPG HJ BAKI
  • SJKCH KRANJI
  • SIMPANG BUDDHIST VILLAGE
  • KAMPUNG SINIAWAN BARU
  • TAMAN SINIAWAN 1
  • TAMAN SINIAWAN 2
  • KAMPUNG PODAM
  • SMK PAKU
  • TOYOTA BORNEO MOBILITY
  • SUBARU KUCHING
  • OPP CHUNG HUA MIDDLE SCHOOL NO 1
  • PETRON PENDING
  • LEMBAGA LADA MALAYSIA HQ
  • LEMBAGA LADA MALAYSIA (TRADE)
  • JETI BAKO
  • KAMPUNG BAKO INDAH
  • DEWAN SERBAGUNA KPG HIJRAH
  • TAMAN MESRA BAKO
  • OPP SMK BAKO
  • MUARA TEBAS
  • SIMPANG MUARA TEBAS
  • SIMPANG KAMPUNG BAKO
  • SENARI PORT
  • OPP TIONG NAM
  • DEMAK INDUSTRIAL PARK
  • JALAN KEMAJUAN
  • WHITE HORSE CERAMIC
  • OPP CONSOLIDATED INDUSTRIES
  • OPP LEMBAGA LADA MALAYSIA (TRADE)
  • OPP LEMBAGA LADA MALAYSIA HQ
  • ANG CHENG HO QUARRY
  • JALAN BATU KAWA 8
  • SJK CHUNG HUA BATU KAWA
  • BATU KAWA COMMERCIAL CENTER
  • ELM MACHINERY
  • JALAN SEGEDUP
  • DESA WIRA
  • MJC CITY 1
  • MJC CITY 2
  • OPP LAU FURNITURE
  • OPEN AIR MARKET
  • JKR BATU LINTANG
  • KWB
  • ARENA SUKAN
  • CONDO FLORIDALE
  • OPPOSITE VIVACITY
  • TABUAN JAYA
  • EMART TABUAN JAYA
  • PJS
  • UNI VISTA
  • HOSPITAL UNIMAS
  • BATU 16 KUCHING SERIAN
  • KAMPUNG DURAS
  • INSTITUT MEMANDU SIBURAN
  • PASAR SIBURAN
  • CHUNG HUA SIBURAN
  • KOMPLEKS SUKAN PADAWAN
  • OPP UNACO SIBURAN
  • BERATOK
  • SJK TAPAH
  • TAMAN HARMONI - SIBURAN
  • KAMPUNG RITUH LABUAN
  • KAMPUNG RITUH PELAMAN
  • JALAN KUCHING SERIAN 1
  • SK GEMAN
  • SJK CHUNG HUA BATU 29
  • KAMPUNG TIAN MAWANG
  • SUNGAI MAMAT
  • JALAN KUCHING SERIAN 2
  • SJK CHUNG HUA BATU 32
  • TARAT
  • TARAT JAYA
  • JALAN KUCHING SERIAN 3
  • JALAN KUCHING SERIAN 4
  • KAMPUNG STABUN
  • OPPOSITE HOSPITAL SERIAN
  • IPD SERIAN
  • STESEN BAS SERIAN
  • SEB SERIAN
  • ROXY HOTEL SERIAN
  • HOSPITAL SERIAN
  • FLYOVER SERIAN
  • OPP TAMAN AYER MANIS
  • OPPOSITE JALAN KUCHING SERIAN 2
  • SUNGAI RAYANG SIJO
  • SJK CHUNG HUA BATU 35
  • TARAT JAYA FOOD JUNCTION
  • OPPOSITE TARAT
  • OPPOSITE SJK CHUNG HUA BATU 32
  • OPPOSITE KAMPUNG TIAN MAWANG
  • OPPOSITE SJK CHUNG HUA BATU 29
  • KAMPUNG LINTANG BARU
  • GEMANG
  • OPP SIMPANG JALAN KONG PING
  • OPPOSITE KAMPUNG RITUH MAWANG
  • OPOSITE KAMPUNG RITUH LABUAN
  • OPPOSITE TAMAN HARMONI
  • OPPOSITE SJK TAPAH
  • OPPOSITE BERATOK
  • UNACO SIBURAN
  • IPD PADAWAN
  • SIBURAN
  • SMK SIBURAN
  • TAMAN DURAS
  • OPP BATU 16 KUCHING SERIAN
  • OPPOSITE UNIMAS
  • SMK TABUAN JAYA
  • SARAWAK SKILLS
  • TABUAN JAYA 1
  • TABUAN JAYA 2
  • VIVACITY
  • JALAN WAN ALWI 1
  • JALAN WAN ALWI 2
  • BATU LINTANG 1
  • BATU LINTANG 2
  • BOMBA BATU LINTANG
  • OPPOSITE JKR BATU LINTANG
  • KOZY SQUARE
  • ST3
  • BAHTERANGKUT
  • OPP SGH
  • INDIAN ASSOCIATION
  • DEMAK INDUSTRIAL PARK ROUNDABOUT
  • OPP SK PAJAR SEJINGKAT
  • OPP SEB SUBSTATION SEJINGKAT
  • TAMAN PERINDUSTRIAN CENTRAL LIGHT
  • TERMINAL SAUJANA
  • OPP SUNNY HILL
  • TAMAN SRI EMAS
  • and 156 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

13 findings, ordered by severity.

Show every finding
  • Error6352 instances

    Stop time with arrival before previous departure time (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules

  • Warning620 instances

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

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

  • Warning406 instances

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

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

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

  • Info399 instances

    About 399 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info2 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 161 days.
Accessible Not yet
States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 161 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 6352 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 44 / 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 Kuching 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-kuching/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.