Feed status · checked 2026-10-17
TransLink Bowen
Based on the official feed source on file
Service mode Bus
down 1.4 since 2026-10-16
Cataloged in Queensland, Australia.
Source feed: https://gtfsrt.api.translink.com.au/GTFS/BOW_GTFS.zip Version history on the Mobility Database
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.4, validator 8.0.1.
Checked for changes 3 hours ago; last changed 9 hours 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.
About this feed
TransLink Bowen’s published feed lists 4 bus routes, 32 scheduled trips and 81 stops. Its service dates run from 2026-10-17 through 2026-12-16. The published file last changed on 2026-10-17.
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
81 of 81 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.
Fixing this covers all 81 stops in the feed.
⏱ 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
32 of 32 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 32 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
Fix 01 · 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.
Fix 02 · 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.
Fix 03 · Read the fix guide for scorecard_no_fare_data
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 60 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 8 instances (0 error, 8 warning, 0 informational).
Service data covers the next 60 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
41 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Livingstone St near Herbert St hail 'n' ride", "Herbert St near Daniel St hail 'n' ride", "Gregory St near Scott St hail 'n' ride", 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 81 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.
- 841 (pink)
- 842 (pink)
- 843 (pink)
- 844 (pink)
| Route | Type | Line color |
|---|---|---|
| 841 Queens Beach | Bus | pink |
| 842 Harbour Loop | Bus | pink |
| 843 Rose Bay | Bus | pink |
| 844 Town Loop | Bus | pink |
List every stop
- Williams Street at Gregory Street
- Williams Street at Sinclair Street
- Gregory Street at Williams Street
- Herbert Street at Powell Street
- Gregory Street at Bowen Hospital
- Livingstone St near Herbert St hail 'n' ride
- Herbert St near Daniel St hail 'n' ride
- Gregory St near Scott St hail 'n' ride
- Gregory Street near Carleton Street
- Gregory St near Banksia St hail 'n' ride
- Richmond Road at Centre Point Plaza
- Tollington Rd near Soldiers Rd hail 'n' ride
- Tollington Rd near Wests Lane hail 'n' ride
- Wests Lane at Tollington Road
- Wests Lane at North Court
- Wests Lane at Argyle Park Road
- Argyle Park Road at Duke Street
- Mackenzie St near Field St hail 'n' ride
- Field Street near Webster Street
- Golf Links Rd near Strickland St hail 'n' ride
- Golf Links Rd near Lloyds Lane hail 'n' ride
- Murroona St near Bryant Ave hail 'n' ride
- Murroona Street at Beach Avenue
- Murroona Street at Murray Avenue
- Scott Avenue at Whitsunday Street
- Gloucester St near Clement Ave hail 'n' ride
- Gloucester St near Murray Ave hail 'n' ride
- Tracey St near Beach Ave hail 'n' ride
- Tracey Street at Bryant Avenue
- Golf Links Road at Mt Nutt Road
- Golf Links Rd near Strickland St hail 'n' ride
- Field St near Strickland St hail 'n' ride
- Tollington Road at Argyle Park Road
- Tollington Rd near Wests Lane hail 'n' ride
- Argyle Park Rd near Suthers St hail 'n' ride
- Argyle Park Road at Emmerson Drive
- Argyle Park Road at Rosshall Street
- Hillview Rd near Soldiers Rd hail 'n' ride
- Hillview Road at Hammond Street
- Herbert St near Livingston St hail 'n' ride
- Livingstone Street at Leichhardt Street
- Brisbane St near William St hail 'n' ride
- Santa Barbara Parade at Starboard Drive
- Soldiers Road at Verna Street
- Argyle Street at Howard Street
- Horseshoe Bay Road at St Kilda Street
- Horseshoe Bay Rd near Crofton St hail 'n' ride
- Horseshoe Bay Road at Prentice Street
- Bluewater Parade at Bluewater Parade
- Horseshoe Bay Road at Murray Bay Road
- Horseshoe Bay Road at Prentice Street
- Coral Street at Holborne Street
- Horseshoe Bay Rd near Soldiers Rd hail 'n' ride
- Soldiers Rd near Verna St hail 'n' ride
- Soldiers Rd near Robe St hail 'n' ride
- John St near Richmond Rd hail 'n' ride
- John Street at Sunset Crescent
- John St near Sunset Cr hail 'n' ride
- Christison Street at Rayner Street
- Christison St near Russell St hail 'n' ride
- Pantall Street at Canberra Street
- Pantall St near Don St hail 'n' ride
- Belgravia Road at Reynolds Street
- Reynolds Street at Gillies Street
- Reynolds St near Mitchell St hail 'n' ride
- Mitchell St near Bunting St hail 'n' ride
- Kennedy Street at Mitchell Street
- Kennedy St near Norris St hail 'n' ride
- Norris Street at Poole Street
- Norris St near Gordon St hail 'n' ride
- Powell St near Norris St hail 'n' ride
- Powell Street at Mitchell Street
- Mitchell St near William St hail 'n' ride
- George Street at Mitchell Street
- Leichhardt Street at George Street
- Dalrymple St near Gregory St hail 'n' ride
- George St near Herbert St hail 'n' ride
- Herbert St near Poole St hail 'n' ride
- George St near Gregory St hail 'n' ride
- Herbert St near Scott St hail 'n' ride
- Crofton St near Tea Tree Pl hail 'n' ride
Over time
Overall score across the last 16 checks — down 1.4 since 2026-10-16.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 73.9 | first check |
| 2026-10-03 | 74.3 | up 0.4 |
| 2026-10-04 | 73.9 | down 0.4 |
| 2026-10-05 | 73.9 | no change |
| 2026-10-06 | 73.9 | no change |
| 2026-10-07 | 73.9 | no change |
| 2026-10-08 | 76.1 | up 2.2 |
| 2026-10-09 | 75.7 | down 0.4 |
| 2026-10-10 | 74.3 | down 1.4 |
| 2026-10-11 | 73.9 | down 0.4 |
| 2026-10-12 | 73.9 | no change |
| 2026-10-13 | 76.1 | up 2.2 |
| 2026-10-14 | 75.7 | down 0.4 |
| 2026-10-15 | 76.1 | up 0.4 |
| 2026-10-16 | 75.7 | down 0.4 |
| 2026-10-17 | 74.3 | down 1.4 |
What changed since your last check
- Correctness down 4.0
- Freshness up 1.7
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-17 | 81e8896792ec | 2026-12-16 | Current rubric: see the trend above |
| 2026-10-15 to 2026-10-16 (2 checks) | 8357529a694f | 2026-12-14 | Current rubric: see the trend above |
| 2026-10-12 to 2026-10-14 (3 checks) | 921d8ca95402 | 2026-12-12 | Current rubric: see the trend above |
| 2026-10-10 to 2026-10-11 (2 checks) | 235a694bce0a | 2026-12-09 | Current rubric: see the trend above |
| 2026-10-07 to 2026-10-09 (3 checks) | 0292cc6d0702 | 2026-12-07 | Current rubric: see the trend above |
| 2026-10-06 | 4d2f27eed420 | 2026-12-05 | Current rubric: see the trend above |
| 2026-10-05 | 6426798f6c0b | 2026-12-05 | Current rubric: see the trend above |
| 2026-10-02 to 2026-10-04 (3 checks) | 4e221e6fbcb9 | 2026-12-02 | Current rubric: see the trend above |
| 2026-09-30 to 2026-10-01 (2 checks) | d53689515cc1 | 2026-11-30 | C, 76.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-29 | dba0e1172f22 | 2026-11-28 | C, 76.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-26 to 2026-09-28 (3 checks) | 54480a0a508b | 2026-11-25 | C, 73.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-22 to 2026-09-25 (4 checks) | 1844f8b345f9 | 2026-11-21 | C, 74.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
Showing the 12 most recent of 42 periods.
What changed in this feed
Overall score fell 1.4 points since 2026-10-16.
The feed file was re-published since 2026-10-16.
New since 2026-10-16 (1 finding)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning81 instances
81 of 81 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)
- Warning32 instances
32 of 32 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.)
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)
- Warning6 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · 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)
- 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 60 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 60 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 86 / 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 100 / 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 Australia portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Queensland
Other scorecards in Queensland, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/translink-bowen/2026-10-17.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-10-17. 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.