Feed status · checked 2026-07-18
Unilink (Southampton)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Southampton, United Kingdom.
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
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
259 of 259 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
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
882 of 882 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
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.
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.
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.
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 63 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
The MobilityData validator flagged 3 kinds of issue across 3 instances (0 error, 2 warning, 1 informational).
Service data covers the next 63 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
11 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("B&Q House", "ASDA & Marlands [AJ]", "ASDA & Marlands [AK]", 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.
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 dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 28 (white)
- 28A (white)
- U1A (white)
- U1C (white)
- U1E (white)
- U2B (white)
- U2C (white)
- U6C (white)
- U6H (white)
- U9 (white)
| Route | Type | Line color |
|---|---|---|
| 28 | Bus | white |
| 28A | Bus | white |
| U1A | Bus | white |
| U1C | Bus | white |
| U1E | Bus | white |
| U2B | Bus | white |
| U2C | Bus | white |
| U6C | Bus | white |
| U6H | Bus | white |
| U9 | Bus | white |
This feed has 259 stops.
List every stop
- Chandlers Ford, Asda
- Chandlers Ford, Asda
- Falkland Road
- Falkland Road
- Avenue Park
- Avenue Park
- The Cricketers
- The Cricketers
- Airport Parkway Station
- Southampton Airport
- Chestnut Avenue, Barton Peveril College
- Chestnut Avenue, Barton Peveril College
- Eastleigh College
- Eastleigh College
- Doncaster Road
- Doncaster Road
- York Road
- York Road
- Airport Parkway Station
- Derby Road
- Derby Road
- Campbell Road
- Campbell Road
- The Swan Centre
- Eastleigh Railway Station
- Eastleigh Bus Station [A]
- The Chilworth Arms
- The Chilworth Arms
- The Orchard
- The Orchard
- Green Lane
- Green Lane
- Pinelands Road
- Pinelands Road
- Birch Road
- Birch Road
- Bassett, Chilworth Roundabout
- Lakeside Country Park
- Lakeside Country Park
- Chestnut Avenue, Asda
- Royal Mail Centre
- Monks Way
- Monks Way
- B&Q House
- Chestnut Avenue, Asda
- Enterprise Road
- Fibercore House
- Fibercore House
- Southampton Science Park, Benham Campus
- Woodmill Lane
- Belmont Road
- St Denys Church
- St Denys Church
- Priory Road
- Priory Road
- Wakefield Road
- Meggeson Avenue, Townhill Way
- Holyrood Church [BK]
- Holyrood Church [BJ]
- Bassett, Chilworth Roundabout
- Aster Road
- High Road
- High Road
- Walnut Avenue
- NOCS
- Southampton, Westquay [BP]
- Civic Centre [AI]
- Friars Way
- Friars Way
- Highfield Interchange [B]
- Bassett Green, Lobelia Road
- General Hospital, Tremona Road [D]
- General Hospital, Coxford Road [B]
- General Hospital, Tremona Road [C]
- Springford Crescent
- Springford Crescent
- Lyburn Court
- Lyburn Court
- Hollybrook Roundabout
- Hollybrook Roundabout
- Bassett Sainsbury's
- Bassett Sainsbury's
- Winchester Road, Great Oaks School
- Butterfield Road
- Butterfield Road
- Winchester Road, Great Oaks School
- Bassett Crescent
- Holly Hill
- Bassett Crescent
- Bassett Crossroads
- Bassett Crossroads
- Boldrewood Campus
- Boldrewood Campus
- Hartley Grove
- Hartley Grove
- Elmsleigh Gardens
- Glen Eyre Road
- Glen Eyre Road
- Burgess Road Library
- Future Worlds
- Burgess Road Library
- Tulip Road
- Bealing Close
- Bealing Close
- Daisy Dip
- Woodcote Road
- Tulip Road
- Aster Road
- Aster Road
- Swaythling McDonald's
- Woodmill Lane
- Mayfield Road
- Mayfield Road
- Sirdar Road
- Wessex Lane Halls
- Wessex Lane Halls
- Swaythling Station
- Swaythling Station
- Walnut Avenue
- General Hospital, A&E [H]
- General Hospital, A&E [G]
- Dale Valley Road
- Dale Road
- The Range
- Vincent Avenue
- The Malvern
- The Malvern
- Leicester Road
- Leicester Road
- Richard Taunton College, Hill Lane
- Richard Taunton College, Hill Lane
- Kineton Road
- Kineton Road
- Jubilee Sports Hall
- Jubilee Sports Hall
- Upper Shaftesbury Avenue
- Upper Shaftesbury Avenue
- Highfield Crescent
- Highfield Crescent
- Portswood Broadway [PA]
- Portswood, The Mitre [PK]
- Portswood Waitrose [PF]
- Portswood Waitrose [PE]
- Portswood Waitrose [PD]
- Tennyson Court
- Tennyson Court
- Bentley Court
- Bentley Court
- Portswood Sainsbury's [PI]
- Portswood Sainsbury's [PJ]
- Sirdar Road
- Bowden Lane
- Oaktree Road, Hop Inn
- Oaktree Road, Hop Inn
- Dimond Road
- Dimond Road
- Wellington Road
- Bond Road
- Northfield Road
- Bowden Lane
- Belmont Road
- Bitterne Park Triangle
- Bitterne Park Triangle
- Nursery Road
- Wellington Road
- Ashtree Road
- Cornwall Road
- Midanbury, Witts Hill Shops
- Community Centre
- Bridlington Avenue
- Bridlington Avenue
- St John's Church
- St John's Church
- Wilton Road
- Wilton Road
- Atherley Bowling Club
- Northland Gardens
- Greville Road
- Northlands Road
- Albany Park Court
- The Avenue, Northlands Road
- The Avenue, Stag Gates
- Stag Gates
- The Avenue, Archers Road
- The Avenue, Archers Road
- Bevois Valley Aldi
- Bevois Valley Aldi
- Forster Road
- Spring Crescent
- Spring Crescent
- Portswood Waitrose [PC]
- Vale Drive
- Townhill Way, Bramble Mews
- Southampton Central Station [SB]
- Southampton Central Station [SA]
- Southampton Central Station [SF]
- Giddy Bridge
- Art Gallery [HE]
- Cenotaph [HA]
- Civic Centre [AO]
- New Road
- Law Courts
- Law Courts
- Denzil Avenue
- Denzil Avenue
- Royal South Hants Hospital
- Royal South Hants Hospital
- ASDA & Marlands [AJ]
- Townhill Park, Pinefield Road
- Broadwater Road
- River Walk
- Albany Park Court
- Twyford Avenue
- Elmsleigh Gardens
- Solent University [ID]
- Solent University [IC]
- Mount Park
- Mount Park
- Bassett Wood Road
- Ridgemount Avenue
- Holly Hill
- Saxholm Way
- Saxholm Way
- Ridgemount Avenue
- ASDA & Marlands [AK]
- Oakmount Avenue
- Avenue Subway
- Avenue Subway
- Oakmount Avenue
- Portswood Broadway [PH]
- Portswood Broadway [PB]
- Art Gallery [HG]
- Cenotaph [HD]
- Aldermoor Turning Circle
- Southampton Crematorium
- Omdurman Road
- Glenwood Avenue
- Southampton, Westquay [BR]
- Avenue Campus
- Town Quay, Platform Tavern [TD]
- Town Quay, Platform Tavern [TC]
- Telephone House [TE]
- Telephone House [TF]
- Furzedown Road
- Park Walk [AH]
- Giddy Bridge
- Westbrook Court
- Cantell School
- Montgomery Road
- Benhams Road
- and 9 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
8 findings, ordered by severity.
Show every finding
- Warning882 instances
882 of 882 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 (opens the GTFS Schedule reference on an external site)
- Warning259 instances
259 of 259 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 (opens the GTFS Schedule reference on an external site)
- 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 (opens the validator rules on an external site)
- Warning1 instance
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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens GTFS Best Practices on an external site)
- Info1 instance
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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
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 63 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 63 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 92 / 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 37 / 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.
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/unilink-southampton/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.