← All agencies

Feed status · checked 2026-09-07

Mwasalat (Oman National Transport Company)

Based on the official feed source on file

Service mode Bus

FDCBA

62.5 / 100

unchanged since 2026-09-06

Catalogued in Oman.

Covers 1058 daysAccessibility gapsRealtime not yet published

The feed is served from Mwasalat's official AVL subdomain. Mwasalat labels its published route data as open data, and Oman's national open data license supplies the reuse terms.

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 6 hours ago; last changed 6 hours 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

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

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

3226 of 3226 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 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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 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: 727 of 727 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

Agency: Mwasalat (Oman National Transport Company)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 727 of 727 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/mwasalat-oman/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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.

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.
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. See this feed's finding-clearance log.
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. · 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 1058 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.

Hi,

Our GTFS feed (Mwasalat (Oman National Transport Company)) scored D (62.5 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 727 of 727 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 3226 of 3226 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/mwasalat-oman/

Score by category

Correctness59.0 / 100

The MobilityData validator flagged 8 kinds of issue across 461 instances (0 error, 453 warning, 8 informational).

Freshness100.0 / 100

Service data covers the next 1058 days.

Rider experience37.5 / 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.

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.

This feed has 727 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.

100 (blue)
100 (blue)
10 (blue)
10 (blue)
12 (blue)
12 (blue)
1 (blue)
1 (blue)
202 (blue)
203_2 (blue)
203 (blue)
203 (blue)
20A (blue)
20A (blue)
20B (blue)
20B (blue)
21 (blue)
21 (blue)
2 (blue)
2 (blue)
3 (blue)
3 (blue)
41 (blue)
41 (blue)
4 (blue)
4 (blue)
51 (blue)
51 (blue)
53 (blue)
53 (blue)
55 (blue)
55 (blue)
5 (blue)
5 (blue)
6 (blue)
6 (blue)
7 (blue)
7 (blue)
8 (blue)
8 (blue)
9 (blue)
9 (blue)
A1 (blue)
A1 (blue)

Routes in Mwasalat (Oman National Transport Company)'s feed
Route	Type	Line color
100 Route 100-S1	Bus	blue
100 Route 100-S2	Bus	blue
10 Route 10-S1	Bus	blue
10 Route 10-S2	Bus	blue
12 Route 12-S1	Bus	blue
12 Route 12-S2	Bus	blue
1 Route 1-S1	Bus	blue
1 Route 1-S2	Bus	blue
202 Route 202-S2	Bus	blue
203_2 Route_203_2-S1	Bus	blue
203 Route 203-S1	Bus	blue
203 Route 203-S2	Bus	blue
20A Route 20A-S1	Bus	blue
20A Route 20A-S2	Bus	blue
20B Route 20B-S1	Bus	blue
20B Route 20B-S2	Bus	blue
21 Route 21-S1	Bus	blue
21 Route 21-S2	Bus	blue
2 Route 2-S1	Bus	blue
2 Route 2-S2	Bus	blue
3 Route 3-S1	Bus	blue
3 Route 3-S2	Bus	blue
41 Route 41-S1	Bus	blue
41 Route 41-S2	Bus	blue
4 Route 4-S1	Bus	blue
4 Route 4-S2	Bus	blue
51 Route 51-S1	Bus	blue
51 Route 51-S2	Bus	blue
53 Route 53-S1	Bus	blue
53 Route 53-S2	Bus	blue
55 Route 55-S1	Bus	blue
55 Route 55-S2	Bus	blue
5 Route 5-S1	Bus	blue
5 Route 5-S2	Bus	blue
6 Route 6-S1	Bus	blue
6 Route 6-S2	Bus	blue
7 Route 7-S1	Bus	blue
7 Route 7-S2	Bus	blue
8 Route 8-S1	Bus	blue
8 Route 8-S2	Bus	blue
9 Route 9-S1	Bus	blue
9 Route 9-S2	Bus	blue
A1 Route A1-S1	Bus	blue
A1 Route A1-S2	Bus	blue

List every stop

Al Saadah
Al Mahaj
Samad R/A Towards Sinaw
Samad R/A Towards Muscat
Al Rudhah Towards Muscat
Al Rudhah Towards Sinaw
Khatmat Milaha Boarder (UAE)
Khatmat Milaha Boarder (Oman)
Haima
Al Mudhaibi Souq Towards Muscat
Ferry Terminal
Salalah Terminus
Al Mudhaibi - Luzaq Towards Sinaw
Al Mudhaibi - Luzaq Towards Muscat
Al Mudhaibi Souq Towards Sinaw
Sinaw R/A
Sinaw R/A - Shell Fuel Stn.
Sinaw Souq
Adam
Mwasalat Office Suhar
Jubail Bus Station
Khatm Al Shiklah Boarder
Azaiba Bus Station
Wadi Adei Tunnel
Karsha
Mintarib Souq
Wadi A'sail Towards Muscat
Muhoot - Opposite Muhoot Municipality
Shannah
Wadi A'sail Towards Shannah
Muhoot - Opposite Muhoot Police Stn.
Muhoot - Muhoot Municipality
Muhoot - Muhoot Police Stn.
Qitbeit Zone
Thamrait
Bahla jubrieen_2
Burj Al Sahwa Station
Al Mudhaibi - Before Bridge
Al Khuwair - Ministry of Housing
Social Protection fund
Municipal Recreation center
Mwasalat Bus Station
Salalah Airport
Al Jubah
Al Ain Central Bus Station
Salalah Grand Mall
Um Algawaref bridge
Al Nahda Center
Al Misfa Roundabout
Al Khuwair - Ministry of Interior
Al Raazi Health Center
Industrial Area OVAL Company
Awqad Traffic Light
Hay wadi al khalil 1
Port Accomodation
Al Ghubra - Shell Fuel Stn.
Mall of Oman
Wadi Kabir - Shell Fuel Stn 1
Bousher Elementary School
Wadi Kabir - Masjid Al Jalalah
Arwa Bint Abdul Mutalib School
Opposite Panorama Mall
Toyota Service Center
Al Shomoukh International School
As Sunainah
Nizwa - UTPS
OQ Base Industries
SQUare
Al Khoudh Traffic Light
Al Bahja Roundabout
University of Technology and Applied Sciences
As Sunainah - Al Maha Fuel St.
Al Salam St. Al Maha Fuel Stn.
Al Ghubra Bridge
Sultan Qaboos Grand Mosque
Al Mabelah Industrial Roundabout
Al Awabi - Majan Shipping and Transport Co.
Al Zulfa Roundabout
Opposite Ellesmere Muscat International School
Al Awabi St.
Jufneen
Opposite SQU Hospital
Al Azaiba - Oman Arab Bank
Dhank R/A Towards Al Buraimi
Dhank R/A Towards Muscat
Sareh Al Elm School
Jufneen - Shell Fuel Stn.
Al Mawaleh Private School
Al Nahdha Hospital
Al Mabelah Bus Station
Al Mawaleh - China Market
Opposite Al Nahdha Hospital
Al Misfa Industrial - Opposite Abraj Energy Services
Wadi Kabir - Modern Dairy Factory
Al Misfa Industrial - Opposite Muscat Industries and Services
Al Misfa Industrial
Panorama Mall
Al Misfa Industrial - Arab Weavers Furniture
Al Misfa Industrial - Abraj Energy Services
Al Misfa Industrial - Opposite Arab Weavers Furniture
Al Duraiz - After Oman Oil Stn.
Al Misfa Industrial - Muscat Industries and Services
Al Duraiz - Shell Fuel Stn.
Al Ghubra St. Intersection
Al Hail South - Al Huda St.
Al Misfa Industrial - Opposite Gulf Engineering Global
Opposite Salalah Vacational College
SQU Hospital
Fanja - Shell Fuel Stn.
Al Ghubra - Muscat Inn Hotel
Saih Al Ahmar - Fanja Club
Fanja - Jamea S.Q
Fanja Hights
Al Azaiba - MAN Truck
Al Mazim Towards Muscat
Ruwi - Al Jami St.
Al Mazim Towards Al Buraimi
Oman Chamber of Commerce and Industry
Industrial Block 2
Al Mabelah Police Station
Al Mabelah - Oman Oil Stn.
Opposite Indian School Bousher
Al Riyam
Indian School Bousher
Romail (Wadi Bani Khalid) Zone
Wadi Adei School
Al Azaiba - Al Khalil Mosque
Al Hail North - Pedestrian Bridge
Al Azaiba - Opposite Al Khalil Mosque
Hellat As Sadd
Wadi Hattat - Souq
Jamea Al Sadeq Al Ameen
Royal Court Affairs Transportation
Omar bin Al Khattab Institute
Al Mabelah - Al Nur St.
Jamea Othman Bin Affan
Opposite Roaa Al Mostaqbal School
Al Khair St.
Opposite - Al Mabelah Badr Al Samaa Hospital
Al Khuwair - Badr Al Samaa Hospital
Awqad Roundabout - Oman Oil Stn.
Roaa Al Mostaqbal School
Opposite Hayy al Shrooq
Wadi Kabir - International School
Al Ghubra - Al Maha fuel Stn.
Oman LNG Bus Stop
Opposite Civil Aviation Authority
Wadi Adei Gate
Ellesmere Muscat International School
Industrial Block 4
Masjid Abdul Redha Sultan
Al Mabelah - Badr Al Samaa
Falaj Al Sham St.
Industrial Area - Rawasco
Al Amerat Roundabout
Al Amerat Gate
Falaj Al Sham
Hay Al Kawther Roundabout
Safeer International Hotel
Al khuwair - Hormuz fuel Station
Salalah - Lulu Hypermarket
Wadi Adai Bridge
Al Mawaleh South - Authority Tax
Al Hail - Peninsula Hotel
Al Mawaleh South Souq
Wadi Adai - Shell Fuel Stn.
Wadi Hattat - Block 1
Opposite Jamea Othman Bin Affan
The Plaza Hotel and Resort
Opposite Awqad Police Station
Industrial Area - Al JISR Shop
Industrial Area - Warehouses Department
Al Hail South St.
Opposite Al Morooj Mall
Al Salam Roundabout
Salalah Port - Training Center
Raysut Roundabout - Al Maha Fuel Stn.
Telecommunications Regulatory Authority
Al Mouj Golf
Wadi Adei St.
Al Azaiba - Al Fardan
Sayyid Sultan bin Ahmed School
Opposite Masjid Khalid Bin Al Waleed
Opposite Oman Refco Pespi
Beit Al Falaj - Shell Fuel Stn.
Al Mabelah Industrial - Danube
Oman Refco Pepsi
Madayn Indutrial Salalah
Seeb International School
Al Mabelah - Al Safa Hypermarket
Opposite Al Mabelah Police Station
Salalah Gardens Mall
Salalah - Opposite Bank Nizwa
Al Ghubrah - Ramez Shopping Center
Al Burj St - Bank Muscat
Wattayah - Car Showroom
Wattayah - Honda
Al Mawaleh South - Al Maha Fuel Stn.
Al Khoudh - Al Maha Fuel Stn.
Al Maabilah - Al Khair Street
Al Mawaleh South - Shell Fuel Stn.
Opposite Azhar Polyclinic
Wadi Hattat - Opposite Block 1
Saih Dhabi Roundabout
Al Barakat St.
Mall of Muscat
Al Saadah - Opposite Oman Post
Al Abiyad - Opp. Shell Fuel St.
Al Wasil Towards Sur
Oman Avenues Mall
Samail - Opposite ROP
Mutrah Souq
Opposite Salalah Gardens Mall
Nizwa - Saal Pedestrian Bridge Towards Bahla
Salalah - Opposite Lulu Hypermarket
Wadi Hatat - Bank Muscat
Wadi Hatat - Opposite Souq
Al Misfa - Opposite Shell Fuel Stn.
Al Khoudh Bridge
Al Azaiba Team Stadium
Oman Cement Company
Al Khuwair - Omantel Bus Stop Towards Ruwi
Knowledge Oasis Intersection
Oasis of Knowledge Traffic Light
Qairoon Hairitti School
Opposite Al Khoudh Police Station
Opposite Qairoon Hairitti School
Industria Area - Nama Dhofar service
Al Khoudh Police Station
Innovation Centre
Knowledge Oasis Muscat
Opposite Port Clinic
Dohat Al Adab St.
Police officers Club
Al Ghubra - Modern System Private School
Masjid Khalid Bin Al Waleed
Madinat Al Nahdah - Jamea Al Nasr
Al Ansab - Al Maha Fuel Stn.
Port Clinic
Al Azaiba - Pedestrian Bridge
Masjid Sad Al Ansab
Al Mawaleh - Al Bahja Center
Al Saadah City Mall
Al Saadah - Market Yabalash
Dar Al Hanan School
Opposite Millennium Resort Salalah
Wadi Kabir - Shell Fuel Stn 2
Salalah Square
Dhofar Municipality
Opposite Royal Omani Amater R.S.
and 477 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-06.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-08-06	61.7	first check
2026-08-07	61.7	no change
2026-09-06	62.5	up 0.8
2026-09-07	62.5	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-06.

The feed file was re-published since 2026-09-06.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

12 findings, ordered by severity.

Show every finding

Warning3226 instances
3226 of 3226 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)
Warning727 instances
727 of 727 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)
Warning194 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning183 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)
Warning51 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)
Warning15 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · 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)
Info4 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info4 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

One requirement remains for this feed to earn 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 1058 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 1058 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 59 / 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 100 / 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 38 / 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.

[![Mwasalat (Oman National Transport Company) GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/mwasalat-oman/badge.svg)](https://gtfsscorecard.org/agency/mwasalat-oman/)

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/mwasalat-oman/2026-09-07.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-07. 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.

GTFS Scorecard. (2026). Mwasalat (Oman National Transport Company) GTFS feed-quality record, dated 2026-09-07 (grade D (62.5/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 6edc3dd342bb…). https://gtfsscorecard.org/data/artifacts/mwasalat-oman/2026-09-07.json

@misc{gtfsscorecard-mwasalat-oman-2026-09-07,
  title        = {Mwasalat (Oman National Transport Company) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/mwasalat-oman/2026-09-07.json}},
  note         = {Checked 2026-09-07; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (62.5/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.