Brightline Trains LLC

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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

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

   Estimated effort: Varies.

2. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

   Estimated effort: Two fields, set once in export settings.

   Agencies here usually clear this within about 1 week (based on 16 observed fixes).

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

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Estimated effort: A small file for most flat-fare systems.

Where this agency stands

Ahead of 80% of all tracked agencies, and ahead of 76% of small agencies nationwide.