Call-prep brief · checked 2026-08-01
Svipper (Troms)
Grade F · 42.3 / 100
Unchanged since 2026-07-31.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three things to fix
Review the rule documentation for 'transfer_with_invalid_trip_and_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Transfer with invalid trip and stop (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
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.
Re-generate shape distances in your export; flag to your vendor if it persists.
Some trips have stop times whose distances along the route go backwards. Apps can show transit vehicles jumping backwards or mis-order stops.
Effort: Usually an export-tool fix, not hand editing.
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
- Transfer with invalid trip and stop (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'transfer_with_invalid_trip_and_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
Key facts
- Feed URL
- https://storage.googleapis.com/marduk-production/outbound/gtfs/rb_tro-aggregated-gtfs.zip
- Last checked
- 2026-08-01
- Service window
- 157 days of service data remain. Last service date 2027-01-05.
- Location
- Troms og Finnmark, Norway
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.