← Back to the full scorecard

Call-prep brief · checked 2026-09-05

Bilbobus

Grade C · 75.9 / 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 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Invalid row length (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

  2. Check the flagged trips in your scheduling software; remove them or restore their missing stops.

    Some trips serve fewer than two stops. A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.

    Effort: Worth a vendor question if it appears often.

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
Invalid row length (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'invalid_row_length' 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

Key facts

Feed URL
https://ctb-gtfs.s3.eu-south-2.amazonaws.com/bilbobus.zip
Last checked
2026-09-05
Service window
298 days of service data remain. Last service date 2027-06-30.
Feed version
1788555737215
Location
Bizkaia, Spain

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.