Brightline Trains LLC

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

   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.

   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.

   Effort: A small file for most flat-fare systems.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Ready

Service data covers the next 295 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

http://feed.gobrightline.com/bl_gtfs.zip

Last checked

2026-07-09

Service window

295 days of service data remain. Last service date 2027-04-30.

State

Florida