GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Borders Buses

Based on the feed this agency publishes

Service mode Bus

54.9 / 100

First scorecard for this agency

Catalogued in Scottish Borders, United Kingdom.

Covers 519 daysAccessibility gapsRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

1294 of 1294 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

2565 of 2565 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

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.

⏱ Two fields, set once in export settings.worth about +15 points in its category

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 519 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness50.2 / 100

The MobilityData validator flagged 11 kinds of issue across 5215 instances (0 error, 3373 warning, 1842 informational).

Freshness85.0 / 100

Service data covers the next 519 days.

Rider experience37.5 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 88 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Woodstock Ave Shelter", "Gilston Rd End Lay-by", "Craigend Rd", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 253 (white)
  • 313 (white)
  • 314 (white)
  • 51 (white)
  • 60 (white)
  • 67 (white)
  • 68 (white)
  • 70 (white)
  • 73 (white)
  • G01 (white)
  • H1 (white)
  • H2 (white)
  • H3 (white)
  • P03 (white)
  • P06 (white)
  • P12 (white)
  • X62 (white)
  • X95 (white)
  • 0418 (white)
  • 0918 (white)
  • 235 (white)
  • 267 (white)
  • 32 (white)
  • 464 (white)
  • B1 (white)
Routes in Borders Buses's feed
RouteTypeLine color
253Buswhite
313Buswhite
314Buswhite
51Buswhite
60Buswhite
67Buswhite
68Buswhite
70Buswhite
73Buswhite
G01Buswhite
H1Buswhite
H2Buswhite
H3Buswhite
P03Buswhite
P06Buswhite
P12Buswhite
X62Buswhite
X95Buswhite
0418Buswhite
0918Buswhite
235Buswhite
267Buswhite
32Buswhite
464Buswhite
B1Buswhite

This feed has 1294 stops.

List every stop
  • Albert Street
  • Industrial Estate
  • Sandysike
  • Grahams Arms Hotel
  • Graham Arms
  • Albert Street
  • Halston Hotel
  • car park
  • Apple Tree
  • Waverley Road
  • The Gosling Bridge
  • California Road
  • Market Hall
  • Market Hall
  • Market Hall
  • Moorville Terrace
  • Newfield
  • Knowefield Avenue
  • Chapel Street
  • Market Hall
  • Market Hall
  • Market Hall
  • Moorville Terrace
  • Beechwood
  • Gosling Bridge
  • Lowry Hill road end
  • Lowry Hill Road end
  • Beechwood
  • Waverley Road
  • Greymoor Way
  • Thornton Road
  • Lansdowne Crescent
  • Club Britannia
  • The Crown
  • Howard Arms
  • Earls Lane
  • California Road
  • Newfield
  • Harker Park
  • Garden Centre
  • Church
  • Westlinton
  • Westlinton
  • Church
  • Collingwood Arms
  • Collingwood Arms
  • Roundabout
  • Roundabout
  • Main Road
  • Main Road
  • Tillmouth Park Hotel
  • Tillmouth Park Lodge
  • Village centre
  • Village Centre
  • Village Hall
  • Village Hall
  • Castle entrance
  • Castle entrance
  • Road end
  • Road end
  • Morris Hall
  • Morrishall Farm
  • Morrishall Farm
  • Village
  • Village
  • Farm Cottages
  • Farm cottages
  • Salutation Inn
  • Salutation Inn
  • Village entrance
  • Village entrance
  • Sawmill
  • Sawmill
  • Horncliffe Road End
  • Horncliffe Road End
  • Mill
  • Red Lion
  • Mill
  • Red Lion
  • Horncliffe House
  • Horncliffe House
  • Tower Cottage
  • Tower Cottage
  • Horncliffe Mains Farm
  • Horncliffe Mains Farm
  • Garden Cottage
  • Garden Cottage
  • Coupland road end
  • Bank Top
  • Coupland road end
  • Bank Top
  • Lady Waterford Hall
  • Gainslaw Hill Farm
  • Gainslaw Hill Farm
  • Three Winds
  • Mount Pleasant Farm
  • Mount Pleasant Farm
  • Three Winds
  • Village
  • Akeld Cottages
  • Village
  • Akeld Cottages
  • West Ord road end
  • West Ord road end
  • Whiteadder Bridge
  • Whiteadder Bridge
  • Crossroads
  • Crossroads
  • Brow of the Hill
  • Canty's Terrace
  • Canty's Terrace
  • Brow of the Hill
  • Humbleton Buildings
  • New East Farm
  • Humbleton Buildings
  • New East Farm
  • Village Green
  • Village Green
  • Camphill
  • Camphill
  • Unthank Square
  • Unthank Square
  • Ord House
  • Loughend
  • Ord House
  • Folly Farm
  • Meadow Hill House
  • Meadow Hill House
  • The Pastures
  • Mansefield Road
  • The Pastures
  • Conundrum
  • High Fair
  • Mansefield Road
  • Prior House
  • Conundrum
  • Prior House
  • Estate entrance
  • Estate entrance
  • Goldstone
  • Windmill Way North
  • Post Office
  • Post Office
  • Goldstone
  • Etal Road
  • Windmill Way West
  • Windmill Way West
  • Border Buses Garage
  • Windmill Way East
  • Bus Station
  • Bus Station
  • Ryecroft Way
  • Ryecroft Way
  • Etal Road
  • Etal Road
  • Morrisons Car Park
  • Wooler Bus Station
  • Shielfield Terrace
  • Morrisons
  • Morrisons
  • Number 23
  • Number 23
  • Black Bull
  • Shielfield Terrace
  • Union Brae
  • Union Brae
  • North Road nursing home
  • North Road nursing home
  • Magdelene
  • Number 45
  • Asda
  • Asda
  • Berwick Railway Station
  • Railway Station
  • Cemetery Lodge
  • Cemetery Lodge
  • Number 45
  • Weetwood Ave south end
  • Weetwood Ave north end
  • Retail Park
  • Castlegate Red Lion
  • Castlegate
  • Castlegate
  • Railway Station
  • Middle School
  • Crispin Road
  • St George's Road
  • Crispin Road
  • St Aidan's Road
  • St Aidan's Road
  • Cemetery Lane
  • Retail Park
  • Golden Square
  • St George's Road
  • Turvelaws Farm
  • Turvelaws Farm
  • Cemetery Lane
  • Berwick Academy
  • Askew Crescent
  • Askew Crescent
  • Golden Square
  • Post Office
  • Spittal Hall
  • Post Office
  • Sandyford Bridge
  • Sandyford Bridge
  • Spring Hill
  • Spittal Hall
  • Spittal Hall railway bridge
  • Marygate
  • Chapel Street
  • Bowsden road end
  • Lamb Inn
  • Springhill Lane
  • Wrangham road end
  • Wrangham road end
  • Bowsden road end
  • Lamb Inn
  • Spring Hill
  • Spittal Hall Place
  • Spittal Hall Place
  • Seaview Caravan Park
  • Seaview Caravan Park
  • Barmoor Lane End
  • Barmoor Lane End
  • Northfield
  • Spring Hill
  • Turning Circle
  • Adams Drive
  • Adams Drive
  • Northfield
  • Sea View
  • Sea View
  • Red Lion
  • Blue House
  • Blue House
  • Deputy Row
  • Deputy Row
  • Red Lion
  • West Weetwood
  • Kirklands
  • Derwent Water Terrace
  • Derwent Water Terrace
  • St John's Church
  • St John's Church
  • West Weetwood
  • Oxford Crossroads
  • Oxford crossroads
  • Memorial
  • Kirklands
  • and 1044 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

16 findings, ordered by severity.

Show every finding
  • Warning2565 instances

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

    Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2565 instances

    2565 of 2565 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning1294 instances

    1294 of 1294 stops don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning763 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning18 instances

    Stop has too many matches for shape (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stop_has_too_many_matches_for_shape' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules

  • Warning16 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning4 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning3 instances

    Stops match shape out of order (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

  • Warning2 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Fast travel between far stops (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    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.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: 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. (A small file for most flat-fare systems.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info1834 instances

    Big gap in service (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • Info8 instances

    Trip headsign matches intermediate stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 519 days.
Accessible Not yet
States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 16 of 1294 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 519 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 50 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 85 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 38 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Borders Buses GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/borders-buses/2026-07-18.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-18. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.