GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-19

Svipper (Troms)

Grade F · 42.3 / 100

First check for this agency, so there is no trend yet.

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

No category changes since the last check.

Top three things to fix

  1. 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.

  2. 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.

  3. 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.

Key facts

Feed URL
https://storage.googleapis.com/marduk-production/outbound/gtfs/rb_tro-aggregated-gtfs.zip
Last checked
2026-07-19
Service window
170 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.2, validator 8.0.1.