Feed status · checked 2026-09-02
NOR-WAY Bussekspress
Based on the official feed source on file
Service mode Bus
up 4.4 since 2026-09-01 · F → D
Catalogued in Norway.
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 9 hours ago; last changed 9 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
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
2551 of 2633 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
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
625 of 625 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
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
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
- 2551 of 2633 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
- Feed evidence
- 625 of 625 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
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 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. 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 479 days.
- Published accessibility data
- Accessibility information is stated for 3.1% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 82 instances (0 error, 79 warning, 3 informational).
Service data covers the next 479 days.
3% 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.
3% of stops state accessibility (1% 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.
Not scored yet. Nothing here counts against the grade.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 2633 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.
| Route | Type | Line color |
|---|---|---|
| NW400 Kystbussen | Bus | blue (no shape in feed) |
| NW431 Fjordekspressen | Bus | blue (no shape in feed) |
| FB55 Kaibussen | Bus | blue (no shape in feed) |
| NW150 Beitostølen - Oslo | Bus | blue (no shape in feed) |
| NW192 Konkurrenten | Bus | blue (no shape in feed) |
| FB50 Flybussen Bergen | Bus | blue (no shape in feed) |
| NW130 Trysilekspressen | Bus | blue (no shape in feed) |
| FB90 Flybussen Bardufoss | Bus | blue (no shape in feed) |
| 60 Haukelandsbussen | Bus | blue (no shape in feed) |
| FB80 Flybussen Harstad | Bus | blue (no shape in feed) |
| FB51 Flybussen Åsane | Bus | blue (no shape in feed) |
| FB85 Flybussen Svolvær - Fra flyplass til Svolvær | Bus | blue (no shape in feed) |
| NW420 Sognefjordekspressen | Bus | blue (no shape in feed) |
| NW180 Haukeliekspressen | Bus | blue (no shape in feed) |
| FB82 FB82 Flybussen Narvik - fra Narvik til flyplass | Bus | blue (no shape in feed) |
| FB81 Flybussen Sortland | Bus | blue (no shape in feed) |
| FB40 Flybussen Stavanger | Bus | blue (no shape in feed) |
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
- Stavanger lufthavn
- Stavanger lufthavn
- Arna terminal
- Åsane terminal
- St. Svithuns plass
- Sparkevik
- Sparkevik
- Hågen
- Komediebakken
- Festplassen
- Knarvik terminal
- Knarvik terminal
- 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
- Svolvær sentrum Lofotgata
- Svolvær sentrum Lofotgata
- 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
- Skistar Lodge Trysil
- Elverum skysstasjon
- Terningmoen øst
- Steinsrudmoen Leira
- Steinsrudmoen Leira
- Fagernes skysstasjon
- Fagernes skysstasjon
- 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
- and 2383 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 4.4 since 2026-09-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 59.8 | first check |
| 2026-08-07 | 59.8 | no change |
| 2026-09-01 | 59.2 | down 0.6 |
| 2026-09-02 | 63.6 | up 4.4 |
What changed since your last check
- Correctness up 10.0
- Freshness no change
- Rider experience no change
What changed in this feed
Grade improved from F to D since 2026-09-01.
The feed file was re-published since 2026-09-01 (-26442 KB).
What changed inside the export
- 2 stops left the export.
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
Changed counts
- down 625 of 625 trips don't say whether the vehicle is wheelchair accessible. (655 → 625) (scorecard_wheelchair_accessible_unknown)
- down Some scheduled trips move faster between stops than a bus can. (57 → 45) (fast_travel_between_consecutive_stops)
- down Between two distant stops, the times imply a speed no bus reaches. (14 → 12) (fast_travel_between_far_stops)
- down 2551 of 2633 stops don't say whether a wheelchair user can board there. (2553 → 2551) (scorecard_wheelchair_boarding_unknown)
No longer reported since 2026-09-01 (1 finding)
- Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). (equal_shape_distance_diff_coordinates_distance_below_threshold)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-09-02 the grade moved from F to D. On 2026-09-01 the check no longer reported: some trip headsigns name a stop along the way, not the final destination. On 2026-09-02 the check no longer reported: equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). As of 2026-09-02 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-09-02 Grade went F to D, correctness rose 10 points.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Warning2551 instances
2551 of 2633 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)
- Warning625 instances
625 of 625 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)
- Warning45 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)
- Warning17 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.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning12 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)
- 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.)
Finding code: missing_recommended_field · 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
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.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- 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 to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- 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.)
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 3% 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 479 days.
- Accessible Not yet
- States wheelchair access on 3% 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 479 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 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.
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-09-02.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-02. 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.