Feed status · checked 2026-09-13
Blackpool Transport
Based on the official feed source on file
Service mode Tram + Bus
unchanged since 2026-09-12
Catalogued in Blackpool, United Kingdom.
Heads-up: The score rose 21 points in one step, from 52 on 2026-09-01 to 73 on 2026-09-12. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-09-12). This can be a brief vendor export glitch; watch the next update before acting.
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.3, validator 8.0.1.
Checked for changes 30 hours ago; last changed 7 days ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
1220 of 1220 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
3444 of 3444 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle 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
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
- 1220 of 1220 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 3444 of 3444 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
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 for scorecard_wheelchair_boarding_unknown
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. See this feed's finding-clearance log.
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 for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide for scorecard_missing_feed_info_dates
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. See this feed's finding-clearance log.
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 109 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 277 instances (0 error, 3 warning, 274 informational).
Service data covers the next 109 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
55 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Chads Road", "St Chads Road", "Ansdell St Josephs Church", 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.
This feed has 1220 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (white)
- 10 (white)
- 11 (white)
- 14 (white)
- 18 (white)
- 2 (white)
- 3 (white)
- 4 (white)
- 5 (white)
- 5X (white)
- 5a (white)
- 5b (white)
- 5c (white)
- 6 (white)
- 7 (white)
- 8 (white)
- Tram (white)
| Route | Type | Line color |
|---|---|---|
| 1 | Bus | white |
| 10 | Bus | white |
| 11 | Bus | white |
| 14 | Bus | white |
| 18 | Bus | white |
| 2 | Bus | white |
| 3 | Bus | white |
| 4 | Bus | white |
| 5 | Bus | white |
| 5X | Bus | white |
| 5a | Bus | white |
| 5b | Bus | white |
| 5c | Bus | white |
| 6 | Bus | white |
| 7 | Bus | white |
| 8 | Bus | white |
| Tram | Tram / light rail | white |
List every stop
- Ansdell St Josephs Church
- Blackpool Sixth Form
- Birch Street
- Broadway Health Centre
- Cardinal Allen High School
- Albert Street
- Flakefleet School
- House Of Time
- Larkholme Lane
- Devon Avenue
- Rossall Lane
- Shovels Inn
- Green Meadow Lane
- Shard Bridge Inn
- Shovels Inn
- Grasmere Road
- Seafield Road
- Baines High School
- Beech Drive
- Wyre Hotel
- Lawnswood Avenue
- Moorland Road End
- Mossbourne Road
- Wyresdale Avenue
- Moorland Road End
- Wyresdale Avenue
- The Ferns
- Unsworth Avenue
- Fordstone Avenue
- Preesall Police Station
- Pilling Lane
- Rossall School
- Cavendish Road
- Moss Side Lane
- Laurel Drive
- Gardeners Arms
- Meadows Avenue
- Neville Drive
- Mersey Road
- Kingfisher Drive
- Melbourne Avenue
- Springfield Drive
- Ryecroft Corner
- Back Lane
- Rydal Road
- Fleetwood Ferry
- Hambleton Shops
- Lime Grove
- Moss House Lane
- Tithebarn Place
- Eastwood Avenue
- Ash Grove
- Stafford Avenue
- Albert Square
- Aldi Poulton Road
- Knott End Ferry Car Park
- Interchange
- Broadwater Holiday Centre
- Cleveleys Bus Station
- Cala Gran
- McDonalds
- Albert Square
- Nautical College
- Queens Hotel
- Queens Hotel
- Highcross Avenue
- Poulton Church
- Linderbreck Lane
- Beech Drive
- Booths
- Saracens Head
- St Aidens College
- Seven Stars
- Fleetwood Road
- Tennyson Avenue
- Shaftesbury Avenue
- Meadows Ave
- Highcross Avenue
- Trunnah Church
- Poulton Booths
- Carleton Fairway
- Morrisons
- Broadwater Caravan Park
- Cala Gran
- Agnew Road
- Cleveleys Bus Station
- Dorset Avenue
- Shaftesbury Avenue
- Morrisons
- New Road
- Pontins Main Entrance
- Arundel Drive
- Carleton Fairway
- Fairhaven Hotel
- Ryecroft Corner
- Green Meadow Lane
- Barton Square
- Knott End Ferry Car Park
- Dicconson Terrace
- Wood Street
- Staining Road End
- Staining Road End
- Aspire Academy
- Aspire Academy
- Swan Drive
- Cleveleys Crescent
- Nutter Road
- Cleveleys Bus Station
- Rough Lea Road
- Cleveleys
- Swan Drive
- Blackpool Airport
- Stony Hill Avenue
- Squires Gate Station
- Starr Gate
- Thursby Home
- Kilgrimol Gardens
- Highbury Road West
- St Leonards Road West
- Beach Road
- St Annes Square
- St Annes Square
- Our Lady Church
- St Patricks Road South
- Methodist Church
- Albert Road
- Moorland Road
- Lindsay Avenue
- Smithy Lane
- Church Road
- Elms Avenue
- Seafield Road
- Lowther Terrace
- The County
- The County
- Lowther Terrace
- Eden Avenue
- Milner Road
- Lindsay Avenue
- Moorland Road
- Albert Road
- St Albans Road YMCA
- St Patricks Road South
- Our Lady Church
- St Annes Square
- St Annes Square
- North Beach Road
- St Leonards Road West
- Cavendish Road
- Norwood Road
- Kilgrimol Gardens
- Thursby Home
- Fletcher Drive
- Meadowcroft Avenue
- Victoria Hotel
- Cleveleys Square
- Victoria Square
- Victoria Hotel
- St Annes Square
- East Bank Road
- St Thomas Church
- York Road
- Osborne Road
- Denford Avenue
- Queens Manor
- Clifton Hospital
- King Edward VII School
- Eddington Road
- Lake Road North
- Fairhaven Hotel
- South Footbridge
- Willows Ave
- Willows Ave
- South Footbridge
- Lake Road North
- Eddington Road
- King Edward VII School
- Queen's Manor
- Denford Avenue
- Osborne Road
- York Road
- Library
- North Crescent
- Sandhurst Avenue
- Cross Street
- Kendal Road
- Links Hotel
- Grasmere Road
- Highbury Road
- Dawson Road
- Spring Gardens
- Derwent Road
- Meadowcroft
- Kilnhouse Lane
- Kilnhouse Lane
- Derwent Road
- Spring Gardens
- Bowness Avenue
- Dawson Road
- Grasmere Road
- Links Hotel
- St Davids Road North
- Cross Street
- Fleet Street
- Sandhurst Avenue
- St Annes Road East
- Saltcotes Road
- Wordsworth Avenue
- South St
- Lytham Hospital
- Grosvenor Street
- St John's Street
- Station Road
- Morrisons Superstore
- Abbey Road
- Woodville Terrace
- Lytham Square
- Station Road
- Shaftesbury Avenue
- Staining Road
- Moons Farm
- Castle Lane
- Meadow Park
- Bibby Drive
- Bibby Drive
- Meadow Park
- Primary School
- The Newton Arms
- Newton Hall Holiday Centre
- Shaftesbury Avenue
- Westmorland Avenue
- Oxenholme Avenue
- Blythe Avenue
- Cleveleys Park
- Newcastle Avenue
- Belford Avenue
- Croasdale Avenue
- Halton Avenue
- Lincoln Avenue
- Methodist Church
- Rough Lea Road
- Norcross Offices
- Methodist Church
- East Bank Road
- Newton Grove
- Fleetwood Affinity Outlet
- Elm Street
- Newton Grove
- Headroomgate Road
- Normoss Farm
- and 970 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 6 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 55.6 | first check |
| 2026-08-07 | 55.2 | down 0.4 |
| 2026-08-10 | 53.9 | down 1.3 |
| 2026-09-01 | 51.5 | down 2.4 |
| 2026-09-12 | 72.8 | up 21.3 |
| 2026-09-13 | 72.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-09-12 the grade moved from F to C. On 2026-09-13 the check no longer reported: service data runs out in 22 day(s). As of 2026-09-13 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-09-12 Grade went F to C, freshness rose 85 points.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning3444 instances
3444 of 3444 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1220 instances
1220 of 1220 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules 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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info274 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 109 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 107 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 91 / 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.
Part of the United Kingdom portfolio: the same scorecards for every feed we track in that group, on one free page.
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/blackpool-transport/2026-09-13.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-09-13. 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.