GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

NOR-WAY Bussekspress

Based on the feed this agency publishes

Service mode Bus

59.8 / 100

First scorecard for this agency

Catalogued in Norway.

Covers 94 daysAccessibility gapsRealtime not yet published

One of Entur's per-operator GTFS exports, covering the NOR-WAY Bussekspress national express coach network.

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.

Checked for changes 5 hours ago; last changed 5 hours ago.

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

2384 of 2472 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 +24 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

732 of 732 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 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 94 days.
Published accessibility data
Accessibility information is stated for 3.6% 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

Correctness60.8 / 100

The MobilityData validator flagged 9 kinds of issue across 738 instances (0 error, 685 warning, 53 informational).

Freshness85.0 / 100

Service data covers the next 94 days.

Rider experience38.4 / 100

4% of stops state wheelchair accessibility (1% marked accessible, 2% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility2.2 / 100

4% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 8 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St. Svithuns plass", "Gullbakkvegen/Bygdinvegen", "Gullbakkvegen/Bygdinvegen", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

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.

  • NW400 (blue)
  • NW431 (blue)
  • FB55 (blue)
  • NW150 (blue)
  • NW192 (blue)
  • FB50 (blue)
  • NW130 (blue)
  • FB94 (blue)
  • 60 (blue)
  • FB80 (blue)
  • FB51 (blue)
  • NW420 (blue)
  • NW180 (blue)
  • FB82 (blue)
  • FB81 (blue)
  • FB40 (blue)
Routes in NOR-WAY Bussekspress's feed
RouteTypeLine color
NW400 KystbussenBusblue
NW431 FjordekspressenBusblue
FB55 KaibussenBusblue
NW150 Beitostølen - OsloBusblue
NW192 KonkurrentenBusblue
FB50 Flybussen BergenBusblue
NW130 TrysilekspressenBusblue
FB94 Flybussen KirkenesBusblue
60 HaukelandsbussenBusblue
FB80 Flybussen HarstadBusblue
FB51 Flybussen ÅsaneBusblue
NW420 SognefjordekspressenBusblue
NW180 HaukeliekspressenBusblue
FB82 FB82 Flybussen Narvik - fra Narvik til flyplassBusblue
FB81 Flybussen SortlandBusblue
FB40 Flybussen StavangerBusblue

This feed has 2472 stops.

List every stop
  • Båtskardet
  • Skjelsvik knutepunkt
  • Håland nedre
  • Håland nedre
  • Gøytil kryss
  • Plassane
  • Grønli
  • Grønli
  • Huka
  • Huka
  • Hauglandsmyra
  • Løyning kryss
  • Bru
  • Viskjer
  • Breiland
  • Breiland
  • Kvånsli
  • Kvånsli
  • Rogdeli
  • Rogdeli
  • Trysil Hotell
  • Halhjem kai
  • Skreppedalen
  • Sandvikvåg
  • Dale heradshus
  • Pasvikveien
  • Stavanger lufthavn
  • Stavanger lufthavn
  • Arna terminal
  • Åsane terminal
  • St. Svithuns plass
  • Sparkevik
  • Sparkevik
  • Komediebakken
  • Festplassen
  • Knarvik terminal
  • Knarvik terminal
  • Aksdal bussterminal
  • Aksdal bussterminal
  • Aksdal bussterminal
  • Longumkrysset
  • Longumkrysset
  • Grenstøl bussterminal
  • Bagn E16
  • Sandnes bussterminal Ruten
  • Stavanger bussterminal
  • Århus knutepunkt
  • Gvammen knutepunkt
  • Ånestadkrysset
  • Ånestadkrysset
  • Gomsrud
  • Gomsrud
  • Kongsberg Diseplass
  • Kongsberg Diseplass
  • Thon Hotel Harstad
  • Equinor Harstad
  • Kanebogen rv. 83
  • Bagn E16
  • Tangen
  • Farriseidet
  • Farriseidet
  • Haugesund bussterminal
  • Haugesund bussterminal
  • Våg
  • Haugane vest
  • Kopstadkrysset
  • Jektevik terminal
  • Mandalskrysset
  • Mandalskrysset
  • Bergen lufthavn
  • Eiganestunnelen
  • Eiganestunnelen
  • Etne terminal
  • Ølen bussterminal
  • Monan E39
  • Monan E39
  • Langrønningen
  • Fyllingsdalen terminal
  • Fyllingsdalen terminal
  • Nordbygdi
  • Nordbygdi
  • Frønsdal
  • Bergen lufthavn
  • Bergen lufthavn
  • Bergen lufthavn
  • Bromsgård
  • Seljord skysstasjon
  • Skaret
  • Skaret
  • Haukeland hotel
  • SUS Ullandhaug
  • SUS Ullandhaug
  • Briskebyen
  • Meinstad
  • Laksastigneset
  • Innovasjonsparken
  • Innovasjonsparken
  • Rogaland Rideklubb
  • Rogaland Rideklubb
  • Helsfyr T
  • Odda terminal
  • Sjølyst
  • Sjølyst
  • Oslo bussterminal
  • Oslo bussterminal
  • Oslo bussterminal
  • Oslo bussterminal
  • Oslo bussterminal
  • Oslo bussterminal
  • Trysil busstasjon
  • Trysilsenteret
  • Trysilsenteret
  • Trysil Hotell
  • Trysil Turistsenter
  • Kjernmoen
  • Kjernmoen
  • Elverum skysstasjon
  • Terningmoen øst
  • Steinsrudmoen Leira
  • Steinsrudmoen Leira
  • Fagernes skysstasjon
  • Fagernes skysstasjon
  • Fagernes skysstasjon
  • Tingnesøddin Fagernes
  • Tingnesøddin Fagernes
  • Skogen Leira
  • Skogen Leira
  • Breiset Fagernes
  • Breiset Fagernes
  • Nordåk
  • Nordåk
  • Valdres Gjestegard
  • Valdres Gjestegard
  • Anmarkrud Aurdal
  • Anmarkrud Aurdal
  • Onstad Aurdal
  • Onstad Aurdal
  • Aurdal omsorgssenter
  • Aurdal omsorgssenter
  • Aurdal kirke
  • Aurdal kirke
  • Aurdal sentrum Kiwi
  • Aurdal sentrum Kiwi
  • Steinberg Aurdal
  • Steinberg Aurdal
  • Brenn Bjørgo
  • Brenn Bjørgo
  • Knutslie
  • Knutslie
  • Klosbøle E16
  • Klosbøle E16
  • Solvang Aurdal
  • Solvang Aurdal
  • Hovde
  • Hovde
  • Såldsåbø Aurdal
  • Såldsåbø Aurdal
  • Kristianslund Bjørgo
  • Kristianslund Bjørgo
  • Nerre Bjørgo
  • Nerre Bjørgo
  • Sebyøygarden
  • Sebyøygarden
  • Ton Hølldalsfoss
  • Ton Hølldalsfoss
  • Leira E16
  • Leira E16
  • Fossen camping Hølldalsføss
  • Valdresflye
  • Valdresflye
  • Gardli
  • Gardli
  • Beitostølen
  • Beitostølen
  • Stølslie
  • Stølslie
  • Beitostølen helsesportsenter fv. 51
  • Beitostølen helsesportsenter fv. 51
  • Morke
  • Morke
  • Sagastogo
  • Sagastogo
  • Li
  • Li
  • Skammestein
  • Skammestein
  • Kjøk
  • Kjøk
  • Brennevegen
  • Brennevegen
  • Varpet Bygdinvegen
  • Varpet Bygdinvegen
  • Hegge stavkyrkje
  • Hegge stavkyrkje
  • Sælid
  • Sælid
  • Gullbakkvegen/Bygdinvegen
  • Gullbakkvegen/Bygdinvegen
  • Heggenes
  • Heggenes
  • Hedalen
  • Hedalen
  • Perslett
  • Perslett
  • Sørbu
  • Sørbu
  • Djupedal
  • Djupedal
  • Engen
  • Engen
  • Vinstervegen
  • Vinstervegen
  • Moahaugen
  • Moahaugen
  • Bjelbølsstølen
  • Bjelbølsstølen
  • Heimdalen
  • Heimdalen
  • Beitostølen helsesportsenter Resepsjonen
  • Storeføss
  • Moane
  • Moane
  • Skogstad
  • Skogstad
  • Rogne
  • Rogne
  • Eriksonsage
  • Eriksonsage
  • Rogne kyrkje
  • Rogne kyrkje
  • Velta
  • Velta
  • Hovi
  • Hovi
  • Sebuvegen
  • Sebuvegen
  • Skattebu
  • Skattebu
  • Furustrand
  • Furustrand
  • Ygnebrue
  • Ygnebrue
  • Skogen
  • Skogen
  • Tingvang
  • Tingvang
  • Solhaug
  • Solhaug
  • Bygdin hotell
  • Jotunheimvegen
  • and 2222 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

15 findings, ordered by severity.

Show every finding
  • Warning2384 instances

    2384 of 2472 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

  • Warning732 instances

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

  • Warning618 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

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

  • Warning16 instances

    Unexpected enum value (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules

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

  • Warning3 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

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

  • 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.)

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

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt is missing its start/end dates

    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

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)

    Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference

  • Info50 instances

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info3 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 4% 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 94 days.
Accessible Not yet
States wheelchair access on 4% 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 94 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 61 / 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 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.

NOR-WAY Bussekspress 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/norway-bussekspress/2026-07-19.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-19. 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.