Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires · Correct or claim this listing
Feed status · checked 2026-07-13
BAS.MY Kangar
Based on the feed this agency publishes
First scorecard for this agency
Ahead of 39% of all tracked agencies and 37% of mid-size agencies. Operates in Perlis, Malaysia. Comparisons use agencies currently tracked worldwide.
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.1, validator 8.0.1.
Checked for changes 43 minutes ago; last changed 43 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 3 snapshots.
- 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
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
17 of 17 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +35 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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 171 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
- Live-arrival data covered 0% of scheduled trips in the sampled window.
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 8 kinds of issue across 1092 instances (0 error, 1090 warning, 2 informational).
Service data covers the next 171 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
24 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("TMN SENA INDAH/ TMN NORMA", "KOMPLEKS PENYAYANG DR SITI HASMAH", "UNIMAP JEJAWI/SK JEJAWI", 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.
Sampled 3 times: 1 of 3 feeds healthy; 0.0% of scheduled trips had live predictions; 94.8% of vehicles on their route.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- R102 (red)
- R15 (red)
- R14 (red)
- R13 (red)
- R12 (red)
- R11 (red)
- R10 (red)
- R104 (red)
- R105 (red)
| Route | Type | Line color |
|---|---|---|
| R102 KANGAR - KILANG GULA | Bus | red |
| R15 ALOR SETAR - UUM SINTOK VIA JITRA | Bus | red |
| R14 KANGAR - ALOR SETAR VIA JITRA | Bus | red |
| R13 KANGAR - ALOR SETAR VIA KUALA SANGLANG | Bus | red |
| R12 KANGAR - KUALA PERLIS | Bus | red |
| R11 KANGAR - PADANG BESAR | Bus | red |
| R10 KANGAR - CHANGLUN | Bus | red |
| R104 TERMINAL BUKIT LAGI - FELDA CHUPING | Bus | red |
| R105 TERMINAL PADANG BESAR-KAKI BUKIT-TERMINAL PADANG BESAR | Bus | red |
This feed has 455 stops.
List every stop
- TERMINAL BAS SHAHAB PERDANA
- Hospital Alor Setar
- ALOR MALAI
- TERMINAL BUKIT LAGI KANGAR
- HENTIAN PERUMAHAN KILANG GULA
- TERMINAL CHANGLUN
- TERMINAL PADANG BESAR PERLIS
- HENTIAN KAMPUNG SEBERANG RAMAI
- HENTIAN UUM SINTOK
- LAMAN PELANGI BUKIT JERNIH KANGAR
- MASJID AL HUSNI BATU BERTANGKUP JLN KILANG GULA
- KAYANGAN SQUARE KANGAR
- KOMPLEKS ISLAM PERLIS
- PUTRA REGENCY
- PEJABAT POS LAJU
- TMN SENA INDAH/ TMN NORMA
- HOSPITAL TUANKU FAUZIAH
- TABUNG HAJI SERIAB
- SK SERI PERLIS
- GIANT KANGAR cp
- SK RAJA SYED ALWI
- INSTITUT PERGURUAN
- KOLEJ JURURAWAT
- UNIMAP BIO PROSES
- JPJ JEJAWI
- SEK JEJAWI
- KOMPLEKS PENYAYANG DR SITI HASMAH
- NGULANG SELATAN
- MASJID ISLAH
- MASJID IBNU SINA PERAWAN DATO KAYAMAN
- SEK DATO KAYAMAN
- TMN EMAS
- MASJID BUKIT KETERI
- SMK DATO JAAFAR HASSAN
- BUKIT JERNIH
- UPP CHUPING
- SIMPANG KILANG GULA
- SEK BATU BERTANGKUP
- MASJID AL HUSNI BATU BERTANGKUP
- KG SG SERAI
- KG BARU LUBUK MACHANG
- KILANG GULA KANGAR
- BALAI BARU
- SK PAYA cp
- SMK DATO SHEIKH AHMAD cp
- SMA ALMAAD
- MAKAM DIRAJA cp
- SEK TENGKU BUDRIAH
- BATAS LIKU ARAU
- SEK DERMA
- MEGA STAR INN
- SMK SYED HASSAN
- TMN SENA INDAH
- TMN SENA
- MASJID TUN ABDUL RAZAK CP
- SIMPANG TASIK MELATI
- TMN PROGRESIF
- UNIMAP JEJAWI/SK JEJAWI
- MAJLIS PERBANDARAN KANGAR (JEJAWI)
- MASJID MUHAMMADI CP
- SMK SYED SIRAJUDDIN CP
- ALOR LANCANG/TMN SAUJANA IDAMAN
- UNIVERSITI MALAYSIA PERLIS JEJAWI KANGAR
- SK SUBANG GAJAH
- KG ALOR ARA
- KTM ARAU
- SJK HWA AIK
- TMN KENANGA
- PASAR BESAR ARAU
- NAT POKOK GETAH
- MASJID AL MURSYID
- PEKAN PAUH
- BALAI POLIS PAUH CP
- SMK TENGKU BUDRIAH
- POLITEKNIK SYED SIRAJUDDIN
- MRSM ULU PAUH
- UNIMAP PAUH/SEK KEJURUTERAAN
- UNIMAP PAUH/KOLEH KEDIAMAN ABD RAZAK
- GERAI BUAH-BUAHAN SEGAR FAMA
- MASJID ABIDIN
- TMN SERI CHANGLUN
- TMN MIDIN INDAH
- KG SALANG cp
- BATU 2
- BATU 3 1/4
- BATU 3 1/2
- MASJID SIRAJUDDIN
- KG PENGHULU CHOH
- RTM PADANG PAUH
- PADANG PAUH
- ALOR SENA
- PAYA
- KOMPLEKS PERTANIAN
- KG BESERI / KG BUKIT TENIANG
- SK BESERI cp
- TMN BESERI PAYA
- SG BATU HAMPAR
- MRSM BESERI CP
- IKM BESERI
- PERKUBURAN CINA BERSERI
- TOK MEK
- SEMADONG
- KG PAYA KELADI
- PUSAT SERENTI
- MASJID AL-MUSTAGFIRIN
- SG JAROM
- KG TITI TINGGI HILIR CP
- MASJID AL-AZIM cp
- TITI TINGGI
- UNICITI PERLIS
- KG BARU
- MASJID AL-NUR CP
- KG SERI AMAN PERLIS
- FELCRA LUBUK SIREH CP
- SMK RAJA PUAN MUDA TENKU FAUZIAH
- BATU 16
- MASJID JABAL AL-ALA CP
- BATU 16 1
- SMK RAJA PUAN MUDA TENGKU FAUZIAH 1
- FELCRA LUBUK SIREH 1
- KG SERI AMAN 1
- MASJID AL-NUR 1
- KG BARU 1 PERLIS
- UNCITI 1
- KG TITI ULU
- KG SERI KESIRAI
- KG SENA DALAM
- BATU 21 / KOK MAK
- BATU 20
- TMN KASTAM 3
- TMN KASTAM 2
- SRJK (C) KHOO AIK cp
- TMN KEMAJUAN
- TMN SERI MEDAN/TMN CAHAYA
- JABATAN KESIHATAN NEGERI PERLIS cp
- SIMPANG TITI CHAI cp
- PASAR TITI CHAI cp
- SK UTAN AJI CP
- SIMPANG LORONG HAMID SAMAH
- KLINIK DESA KG SURAU cp
- DEWAN KG UJUNG BATU cp
- KUARI GUNUNG MEDAN
- SIMPANG TOK TINA ALUIH cp
- TMN MEDAN SEPAKAT cp
- SIMPANG GUNUNG MEDAN cp
- KG BUKIT KECHIK cp
- KG ALOR MARUS cp
- KLINIK DESA BEHOR LATEH cp
- SK KAYANG cp
- KG TITI SERONG/PERTUBUHAN PELADANG cp
- KRAFTANGAN MALAYSIA PERLIS cp
- KG TELUK BATU 5 cp
- SIMPANG TIGA PADANG BESAR SELATAN cp
- WARUNG KAK ETA
- TMN INDERA INDAH cp
- BALAI POLIS KUALA PERLIS cp
- SMK KUALA PERLIS cp
- KOMPLEKS PERNIAGAAN KUALA PERLIS
- STESEN BAS KUALA PERLIS cp
- LKIM cp
- PANGGUNG WAYANG
- PLAZA KUALA cp
- GERAI MAKAN TMN BUKIT KUBU
- TMN BUKIT KUBU
- UNIMAP KG WAI
- SRJK (C) KHAY BENG cp
- KLINIK DESA SEBERANG RAMAI cp
- MASJID USMANIAH
- LADANG BURUNG UNTA PERLIS
- MASJID JABAL AL-ALA 1
- BATU 15A PERLIS
- BATU 15A 1
- KLINIK KESIHATAN KAKI BUKIT PERLIS cp
- KPJ KANGAR CP
- KG BEHOR TEMAK
- PERTUBUHAN PELADANG
- SMK SYED ALWI
- KG BEHOR LATEH
- KG BEHOR MALI
- SEK AGAMA AL-ISLAHIYAH
- KG SG BUGIS
- BALAI POLIS SIMPANG EMPAT
- KOMPLEKS SIMPANG EMPAT MPK
- SIMPANG UNIMAP
- SHELL SIMPANG EMPAT
- SG PADANG
- PERMATANG BONGOR
- TOK PULAU
- SIMPANG KUALA SANGLANG / MASJID AL-MAGHFIRAH
- SMK SANGLANG
- SIMPANG TIGA SG BARU
- SK SANGLANG
- SIMPANG TIGA PADANG KERIA
- MASJID SIMPANG SANGLANG
- JALAN SEPAKAT
- KLINIK KESIHATAN KUALA SANGLANG 1
- JALAN SEPAKAT 1
- MASJID SIMPANG SANGLANG 1
- SIMPANG TIGA PADANG KERIA 1
- SK SANGLANG 1
- SIMPANG TIGA SG BARU 1
- SMK SANGLANG 1
- SK SANGLANG KEDAH
- KLINIK DESA SANGLANG KEDAH
- PEKAN KERPAN
- SMK AYER ITAM
- AYER ITAM
- MEDAN SELERA AYER ITAM
- PARIT ALOR CHANGILEH
- SIMPANG SG KOROK
- KG JERLUN
- SMK JERLUN
- KG KELOMPANG
- MASJID AL-MAHMUDI
- KG PADANG LALANG
- PEKAN KECIL KUALA SUNGAI
- KLINIK KESIHATAN JALAN PUTRA
- TMN SELAYANG
- SMKA KEDAH
- MASJID AL-HIDAYAH
- SK BEHOR MALI
- KLINIK KESIHATAN KUALA SANGLANG
- SJKC CHIN HUN
- MASJID KG SIMPANG EMPAT KUAR
- KOMPLEKS PERNIAGAAN ALOR JAGGUS
- KOMPLEKS PERNIAGAAN MERGONG JAYA
- TMN RAKYAT
- DEWAN TMN WIRA
- TMN PANDAN
- BANK ISLAM
- SG ANAK BUKIT
- KFC STADIUM
- RHB JALAN BADLI SHAH
- PEKAN RABU
- SMK SULTANAH ASMAA
- MASJID AL BUKHARI
- GIANT
- TMN JAYA
- TMN HIDAYAH
- SMK HUTAN KAMPONG
- TMN MAWAR
- TMN CAHAYA
- PASAR BASAH HUTAN KG
- SK BOHOR
- SMK KEPALA BATAS
- KOLEJ TUDM
- TUDM KEPALA BATAS
- PEKAN KEPALA BATAS
- TMN JALAI JAYA
- KEM TOK JALAL
- and 205 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
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Validator rule: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Validator rule: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning580 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning455 instances
455 of 455 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning429 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 (opens the validator rules on an external site)
- Warning344 instances
344 of 344 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning64 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 (opens the validator rules on an external site)
- Warning17 instances
17 of 17 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning10 instances
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 (opens the validator rules on an external site)
- Warning4 instances
Single shape point (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'single_shape_point' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: single_shape_point · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens GTFS Best Practices on an external site)
- Info403 instances
About 403 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 (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.)
Validator rule: 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Recased shouting stop names 403 changes
For example: ALOR MALAI -> Alor Malai
Recased shouting route names 9 changes
For example: KANGAR - ALOR SETAR VIA JITRA -> Kangar - Alor Setar Via Jitra
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 171 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.
Live predictions vs schedule
94.8% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 171 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 58 / 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 24 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 48 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily 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-kangar/2026-07-13.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-13. 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.