GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

BAS.MY Kuala Terengganu

Based on the feed this agency publishes

Service mode Bus

58.9 / 100

First scorecard for this agency

Catalogued in Terengganu, Malaysia.

Covers 161 daysAccessibility gapsRealtime not yet published

The federally supported BAS.MY stage bus network based in Kuala Terengganu. A 2026-07-22 preflight found 9 routes, 390 trips, 394 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

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

394 of 394 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 02

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

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

Fix 03

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

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.

⏱ Two fields, set once in export settings.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. 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.

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

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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

Correctness69.5 / 100

The MobilityData validator flagged 6 kinds of issue across 554 instances (0 error, 552 warning, 2 informational).

Freshness85.0 / 100

Service data covers the next 161 days.

Rider experience23.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 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

  • 14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("MASJID UNISZA / McDonalds", "MRSM KUALA TERENGGANU / IPG BATU RAKIT", "WISMA TI / KOLEJ KOMUNITI", 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.

  • T100 (red)
  • T10 (red)
  • T20 (red)
  • T30 (red)
  • T11A (red)
  • T11B (red)
  • T22 (red)
  • T21 (red)
  • T31 (red)
Routes in BAS.MY Kuala Terengganu's feed
RouteTypeLine color
T100 KUALA TERENGGANU - CITY FEEDERBusred
T10 KUALA TERENGGANU - JETI MERANGBusred
T20 KUALA TERENGGANU - PASIR PANJANG - KG. LAUT - BUKIT PAYUNGBusred
T30 KUALA TERENGGANU - CHENDERING(UiTM) - MARANGBusred
T11A TERMINAL MBKT - BATU RAKIT (PAGI)Busred
T11B TERMINAL MBKT - BATU RAKIT (PETANG)Busred
T22 TERMINAL MBKT - KUALA BERANGBusred
T21 TERMINAL MBKT - BUKIT PAYONGBusred
T31 TERMINAL MBKT - MARANG via KEDAI BULUHBusred

This feed has 394 stops.

List every stop
  • HENTIAN BAS MAJLIS PERBANDARAN KUALA TERENGGANU 1
  • HENTIAN BAS MAJLIS PERBANDARAN KUALA TERENGGANU 2
  • HENTIAN BAS JETI MERANG
  • HENTIAN COSMOPOINT
  • HENTIAN JABATAN KIMIA
  • HENTIAN YAYASAN PEMBANGUNAN KELUARGA
  • HENTIAN SMA KHAIRIAH JALAN SULTAN OMAR
  • HENTIAN SMA KHAIRIAH JALAN SULTAN MOHAMAD
  • HENTIAN SK GONG KAPAS (OPPOSITE)
  • HENTIAN KOMPLEKS BELIA DAN SUKAN
  • HENTIAN SK PUSAT BUKIT BESAR (OPPOSITE)
  • HENTIAN PASAR BUKIT BESAR
  • HENTIAN SK TENGKU BARIAH (OPPOSITE)
  • HENTIAN SMK TENGKU BADARIAH (OPPOSITE)
  • HENTIAN FLAT GELONG BILAL
  • HENTIAN PERTUBUHAN PELADANG KUALA TERENGGANU
  • HENTIAN PASAR KAMPUNG LAUT
  • HENTIAN KAMPUNG BELUKAR JAMBU
  • SEKOLAH KEBANGSAAN KAMPUNG BUKIT CHENDERING
  • HENTIAN KAMPUNG TITIAN BARU
  • HENTIAN SMK SERI PAYONG
  • EMPORIUM HOCK KEE SENG LAMA
  • HENTIAN SMK SERI PAYONG -1
  • HENTIAN SK BUKIT PAYONG -1
  • HENTIAN KAMPUNG BERANGAN PAK AYU -1
  • HENTIAN KAMPUNG TITIAN BARU -1
  • HENTIAN MASJID KAMNPUNG SURAU PANJANG
  • HENTIAN SK KAMPUNG BUKIT CHENDERING
  • HENTIAN KAMPUNG BELUKAR JAMBU -1
  • HENTIAN PASAR KAMPUNG LAUT -1
  • HENTIAN PELADANG KUALA TERENGGANU -1
  • HENTIAN FLAT GELONG BILAL -1
  • HENTIAN SMK TENGKU BARIAH
  • HENTIAN PASAR BUKT BESAR
  • HENTIAN SK PUSAT BUKIT BESAR
  • HENTIAN KOMPLEKS BELIA DAN SUKAN -1
  • HENTIAN SK GONG KAPAS
  • HENTIAN SMA KHAIRIAH JALAN SULTAN MOHAMAD -1
  • HENTIAN SMA KHAIRIAH JALAN SULTAN OMAR -1
  • HENTIAN YAYASAN PEMBANGUNAN KELUARGA -1
  • HENTIAN PEKAN BUKIT PAYUNG
  • HENTIAN BAS MARANG
  • COSMOPOINT
  • KKIA JALAN AIR JERNIH
  • SMKJC CHONG HWA WEI SENG
  • JPJ KUALA TERENGGANU
  • KLINIK DESA PULAU DUYONG
  • KAMPUNG BUKIT TUMBUH
  • BANGGOL PAUH
  • KAMPUNG BUKIT TOK BENG
  • SRK BUKIT TOK BENG
  • SMK IBRAHIM FIKRI
  • TAMAN SAMUDERA
  • KAMPUNG DUYUNG
  • RESTORAN SRI AMAN SEAFOOD
  • KLINIK KESIHATAN SEBERANG TAKIR
  • KEM ASKAR SEBERANG TAKIR
  • LAPANGAN TERBANG SULTAN MAHMUD
  • HOTEL TABUNG HAJI
  • KOMPLEKS SUKAN NEGERI TERENGGANU
  • SEKOLAH SUKAN MALAYSIA TERENGGANU
  • SABASUN 2
  • KOLEJ VOKASIONAL WAKAF TEMBESU
  • TAMAN SRI TEMUSU
  • SM SAINS SULTAN MAHMUD
  • SMK TEKNIK KUALA TERENGGANU
  • PETRONAS WAKAF BARU
  • TAMAN SRI JAYA
  • TAMAN SETIA JAYA
  • KAMPUNG BARU GONG BADAK
  • EMPORIUM HOCK KEE SENG BARU
  • PERODUA GONG BADAK
  • BALAI POLIS GONG BADAK
  • TAMAN PERUMAHAN GONG BADAK 2
  • TAMAN PERUMAHAN GONG BADAK 1
  • UNISZA PINTU A
  • MASJID UNISZA / McDonalds
  • KLINIK PAKAR UNISZA
  • KUARTERS POLIS GONG BADAK
  • BULATAN KAMPUNG PAK TUYU
  • UNISZA PINTU B
  • KAMPUNG GONG DATUK
  • KAMPUNG GONG PAK JIN
  • KAMPUNG PADANG NENAS
  • MASJID PADANG NENAS
  • BALAI POLIS MENGABANG TELIPOT
  • MRSM KUALA TERENGGANU / IPG BATU RAKIT
  • SK KOMPLEKS MENGABANG TELIPOT
  • KLINIK KESIHATAN BATU RAKIT
  • TAMAN PERUMAHAN WAKAF TENGAH
  • KAMPUNG MENGABANG TELONG 1
  • KAMPUNG MENGABANG TELONG 2
  • KAMPUNG TANJUNG BATU RAKIT
  • TAMAN NIRWANA
  • TAMAN DESA KAYANGAN
  • KAMPUNG BATU RAKIT
  • SK BATU RAKIT
  • HUB BATU RAKIT
  • BALAI POLIS BATU RAKIT
  • KLINIK DESA PANTAI KUALA NERUS
  • KAMPUNG PENGKALAN ATAP 1
  • SURAU PENGKALAN ATAP
  • KAMPUNG PENGKALAN ATAP 2
  • KAMPUNG PENGKALAN ATAP 3
  • KAMPUNG PENGKALAN ATAP 4
  • KAMPUNG MENGABANG LEKOR
  • SMK BATU RAKIT
  • SK PAGAR BESI
  • SBP INTEGRASI BATU RAKIT
  • INSTEP
  • AKADEMI KEPIMPINAN GPMS
  • KAMPUNG MENGABANG PANJANG
  • SEMPADAN SETIU
  • TERENGGANU ENDURANCE PARK
  • SMK LEMBAH BIDONG
  • SK LEMBAH BIDONG
  • KAMPUNG RHU TAPAI
  • RHU TAPAI
  • KAMPUNG LEMBAH BIDONG
  • KAMPUNG MERANG 1
  • KAMPUNG MERANG 2
  • LEMBAGA KENAF DAN TEMBAKAU NEGARA
  • SK MERANG
  • FLAT SRI KOLAM
  • KOLEJ KOMUNITI KUALA TERENGGANU
  • WISMA DARUL IMAN
  • JALAN PEJABAT
  • SK LADANG
  • HOTEL TANJONG VISTA
  • HOTEL GRAND CONTINENTAL
  • DATARAN SHAHBANDAR
  • PASAR BESAR KEDAI PAYANG
  • JALAN BANGGUL
  • JALAN KAMPUNG TIONG
  • HOTEL SERI MALAYSIA
  • POLITEKNIK KUALA TERENGGANU
  • YAYASAN TERENGGANU
  • JABATAN PESAKIT LUAR
  • STADIUM NEGERI
  • HOSPITAL SULTANAH NUR ZAHIRAH
  • PUSAT RAWATAN IBU DAN BAYI
  • PANTAI BATU BUROK
  • DATARAN PANTAI BATU BUROK
  • MEDAN SELERA BATU BUROK
  • KUALA TERENGGANU SPECIALIST HOSPITAL
  • KLINIK KESIHATAN HILIRAN
  • JABATAN PEN NEGERI TERENGGANU
  • SABASUN 1
  • KWSP KUALA TERENGGANU
  • GIANT KUALA TERENNGANU
  • WISMA PELADANG KUALA TERENGGANU
  • MYDIN KUALA TERENGGANU
  • STADIUM SULTAN ISMAIL NASSIRUDIN SHAH
  • SIMPANG PANTAI BATU BUROK
  • HOTEL PERMAI
  • KUALA TERENGGANU SPEC HOSPITAL BARU
  • SMA SULTAN ZAINAL ABIDIN
  • SMK SULTAN SULAIMAN
  • PUSAT PERABOT TM JATI GROUP
  • KAMPUNG KUALA IBAI
  • MASJID TERAPUNG KUALA IBAI
  • SIMPANG TIGA CHENDERING
  • NOOR ARFA BATIK
  • KRAFTANGAN MALAYSIA
  • KILANG APTIV
  • WISMA TI / KOLEJ KOMUNITI
  • UITM KUALA TERENGGANU
  • PEJABAT PENGURUSAN KOLEJ KERAWANG
  • SEK PEND KHAS CHENDERING
  • FLAT DESA KELUARGA KUALA TERENGGANU
  • SIMPANG EMPAT CHENDERING
  • BALAI POLIS CHENDERING
  • WISMA GEOSOIL
  • MASJID RUSILA
  • SIMPANG TIGA RUSILA
  • KAMPUNG RHU RENDANG
  • SHELL RHU RENDANG
  • IPD MARANG
  • SMA KHAIRIAH JALAN SULTAN OMAR
  • SMA KHAIRIAH JALAN SULTAN MOHAMAD
  • Jabatan Kimia
  • Yayasan Pembangunan Keluarga
  • SK Gong Kapas
  • Kompleks Belia Dan Sukan
  • SK Pusat Bukit Besar
  • Pasar Bukit Besar
  • SK Tengku Bariah
  • SMK Tengku Bariah
  • Flat Gelong Bilal
  • Pertubuhan Peladang Kuala Terengganu
  • PASAR KAMPUNG LAUT 1
  • Kampung Belukar Jambu / Klinik Desa Kg Laut
  • SK Kampung Bukit Chendering
  • MASJID KAMPUNG SURAU PANJANG
  • PASAR PEKAN KEDAI BULUH / SMK SULTAN MANSOR
  • Kampung Titian Baru
  • Kampung Berangan Pak Ayu
  • SK Bukit Payong
  • SMK Seri Payong
  • HENTIAN BATU RAKIT
  • TERMINAL MBKT
  • TERMINAL BAS KUALA BERANG
  • HENTIAN BUKIT PAYONG
  • OPPOSITE SMA KHAIRIAH JALAN SULTAN OMAR
  • MASJID LAMA DURIAN BURUNG
  • MASJID AT TAQWA
  • MYDIN GONG BADAK
  • COSMOPOINT TERENGGANU
  • KG LOSONG ATAP ZINK
  • MUZIUM NEGER TERENGGANU
  • MASJID KRISTAL
  • OPPOSITE MUZIUM WARISAN
  • KG LOSONG LEBAI SALLEH
  • OPPOSITE SMK SULTAN AHMAD
  • SEK KEB KEPONG
  • SK KG BAHARU SERADA
  • KG BANGGOL KEMANG
  • KG TIRUK
  • KG PASIR TINGGI
  • SK PASIR TINGGI
  • KG PADANG LIMAU NIPIS
  • KG BINJAI BONGKOK
  • DESA KAYANGAN
  • ALAM MUTIARA 1 & 2
  • PASAR KAMPUNG LAUT 2
  • LORONG TOK KHATIB ALI
  • MASJID BELUKAR JAMBU
  • MSU COLLEGE
  • SMK KHAIRIAH JALAN SULTAN OMAR
  • KUATERS JKR
  • KG GEMIA
  • SMK MEGAT PANJI ALAM
  • TANAH KUBUR ISLAM KG NIBONG ATAS
  • LORONG PARMY
  • KLINIK DESA GONG TOK NASEK
  • ARKED MAIDAM
  • SK GONG TONG NASEK
  • LORONG HJ MAT AMIN
  • LORONG POK HIM
  • PASTI IBNU SINAR
  • SURAU KAMPUNG TONG PONG
  • SK TOK DIR
  • MASJID TOK DIR
  • JALAN BAROH PINANG
  • KAMPUNG ALUR PARIT
  • JALAN PADANG KOLAH
  • MASJID KAMPUNG UDANG
  • ENTERPRENUE PARK BUKIT KOR
  • KOLEJ TASDEC
  • UCSI UNIVERSITY
  • and 144 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
  • Warning394 instances

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

  • Warning390 instances

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

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

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

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

  • Warning2 instances

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Validator rule: stops_match_shape_out_of_order · 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

  • 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

  • Info376 instances

    About 376 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. 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 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. 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 70 / 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 Kuala Terengganu 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-kuala-terengganu/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.