Feed status · checked 2026-09-06
BAS.MY Kuching
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-05
Catalogued in Sarawak, 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.3, validator 8.0.1.
Checked for changes 80 minutes ago; last changed 80 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.
Top things to 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.
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
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 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
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
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.
- Feed evidence
- Stop time with arrival before previous departure time (flagged by the MobilityData validator).
- Next action
- 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.
- 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
- Feed evidence
- Foreign key violation (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- 406 of 406 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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.
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. See this feed's finding-clearance log.
Review the rule documentation for 'foreign_key_violation' 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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 116 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
The MobilityData validator flagged 7 kinds of issue across 3795 instances (3081 error, 712 warning, 2 informational).
Service data covers the next 116 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 not published.
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.
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 406 stops.
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.
- Q01 (red)
- Q10 (red)
- Q05 (red)
- Q06 (red)
- Q07 (red)
- Q08 (red)
- Q09 (red)
- Q13 (red)
- Q14 (red)
| Route | Type | Line color |
|---|---|---|
| Q01 SAUJANA PARKING - TAMAN MALIHAH | Bus | red |
| Q10 OPEN AIR MARKET - TERMINAL BAS SERIAN | Bus | red |
| Q05 SAUJANA PARKING - SMKA MATANG 2 | Bus | red |
| Q06 SAUJANA PARKING - KAMPUNG BENUK | Bus | red |
| Q07 SAUJANA PARKING - SJK CHUNG HUA BATU KAWA | Bus | red |
| Q08 SAUJANA PARKING - TERMINAL BAS BAU | Bus | red |
| Q09 OPEN AIR MARKET - MUARA TEBAS | Bus | red |
| Q11 SAUJANA PARKING - ARANG ROAD | Bus | red (no shape in feed) |
| Q12 SAUJANA PARKING - TAMAN HUI SING | Bus | red (no shape in feed) |
| Q13 OPEN AIR MARKET - SIBURAN | Bus | red |
| Q14 OPEN AIR MARKET - SUMMER MALL | Bus | red |
| Q16 OPEN AIR MARKET - SUKMA | Bus | red (no shape in feed) |
| Q15 STUTONG BARU / KUCHING SENTRAL - SAUJANA PARKING | Bus | red (no shape in feed) |
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
Overall score across the last 4 checks — unchanged since 2026-09-05.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 49.1 | first check |
| 2026-08-07 | 49.2 | up 0.1 |
| 2026-09-05 | 38.6 | down 10.6 |
| 2026-09-06 | 38.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-09-05.
The feed file was re-published since 2026-09-05.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-09-06 the grade held, though the score fell from 49 to 39. As of 2026-09-06 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-09-05 Score fell 11 points, correctness fell 24 points.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Error2912 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.)
Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error169 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning286 instances
286 of 286 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning195 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning117 instances
Between two distant stops, the times imply a speed no bus reaches.
A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.
Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)
Finding code: fast_travel_between_far_stops · 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.)
Finding code: 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- 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.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- 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.)
Finding code: unknown_column · 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).
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 · 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. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 116 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 116 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3081 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 24 / 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.
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-09-06.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-09-06. 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.