AtB

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   13716 of 13719 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.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   20913 of 20913 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

   Effort: A default or per-trip field in your export.

Key facts

Feed URL

https://storage.googleapis.com/marduk-production/outbound/gtfs/rb_atb-aggregated-gtfs.zip

Last checked

2026-07-19

Service window

125 days of service data remain. Last service date 2026-11-21.

Location

Trøndelag, Norway