← All agencies

Feed status · checked 2026-10-22

Slieve Bloom Coach Tours

Based on the official feed source on file

Service mode Bus

FDCBA

85.7 / 100

down 1.5 since 2026-10-21

Cataloged in Ireland.

Covers 364 daysAccessibility gapsRealtime not yet published

Source feed: https://www.transportforireland.ie/transitData/Data/GTFS_Slieve_Bloom.zip

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 39 minutes ago; last changed 6 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

Slieve Bloom Coach Tours’s published feed lists 7 bus routes, 73 scheduled trips and 107 stops. Its service dates run from 2026-10-21 through 2027-10-21. The published file last changed on 2026-10-22.

Top things to fix

Fix 01

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

73 of 73 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 73 trips in the feed.

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

Fix 02

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

Fix 03

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ Often a bulk fix in your scheduling software.worth about +6 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

Agency: Slieve Bloom Coach Tours
Finding: scorecard_wheelchair_accessible_unknown
Feed evidence: 73 of 73 trips don't say whether the vehicle is wheelchair accessible.
Why it matters: Even with accessible stops, riders need to know the bus itself can take them.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/?finding=scorecard_wheelchair_accessible_unknown#finding-handoff

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_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 02 · 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.
Fix 03 · Read the fix guide for mixed_case_recommended_field
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 364 days.
Published accessibility data: Accessibility information is stated for 96.3% 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.

Hi,

Our GTFS feed (Slieve Bloom Coach Tours) scored B (85.7 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 73 of 73 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

2. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
   What: Some rider-facing names are in ALL CAPS or all lowercase.
   Finding code: mixed_case_recommended_field
   Guide: https://gtfsscorecard.org/fix/mixed_case_recommended_field/

Full scorecard: https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/

Score by category

Correctness89.5 / 100

The MobilityData validator flagged 3 kinds of issue across 23 instances (0 error, 22 warning, 1 informational).

Freshness100.0 / 100

Service data covers the next 364 days.

Rider experience69.1 / 100

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

Accessibility60.2 / 100

96% of stops state accessibility (60% marked accessible). Reflects what the feed states, 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.

This feed has 107 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.

827 (green)
829 (green)
830 (green)
831 (green)
832 (green)
837 (green)
838 (green)

Routes in Slieve Bloom Coach Tours's feed
Route	Type	Line color
827 Mountmellick - Portarlington - Portlaoise	Bus	green
829 Portlaoise - Portarlington - Tullamore	Bus	green
830 Portlaoise - Tullamore	Bus	green
831 Portlaoise - Portlaoise	Bus	green
832 Errill - Portlaoise	Bus	green
837 Tullamore - Mullingar	Bus	green
838 Kilkenny - Portlaoise	Bus	green

List every stop

Clogh
Clogh
Moneenroe
Castlecomer
Market Yard
Market Yard
Banim Terrace
Banim Terrace
Castlecomer
Moneenroe
Ballyragget
Castletown
Borris-in-Ossory
Errill
The Swan
Timahoe
Timahoe
Mountmellick Ch
Pike of Rush Hall
Pike of Rush Hall
Coolbanagher
Coolbanagher
Castletown
Stradbally
Doonane
Ballyroan
The Heath
The Heath
Portarlington
Killenard
Old Pound
Kilminchy
Link Road
Link Road
Portarlington Stn
Rathdowney
Mountmellick Ch
Mountmellick
Mountmellick
Newtown
Ballybrittas
Abbeyleix
Abbeyleix
Ballybrittas
Durrow
Portlaoise JFL Ave
Portlaoise Hosp
Portlaoise JFL Ave
Portlaoise JFL Ave
Portlaoise Hosp
Stradbally
Mountrath
Mountrath
St Vincent's Unit
The Swan
Ballinakill
Williamstown Road
Killenard
Ferndale Estate
Emo
Ballyroan
Ballycolla
Emo
Ballinakill
Kilminchy
Portlaoise Stn
Portlaoise Stn
Rathbrennan
Ballacolla
Borris-in-Ossory
Doonane
Errill
Rathdowney
Tullamore Coll
Geashill
Ardan
Ardan
Avondale Estate
Patrick Street
Patrick Street
Garryhinch
Garryhinch
Clonygowan
Tullamore Hospl
Tullamore Stn
Tullamore Stn
Na Cluainte
Tullamore Hospl
Tullamore Hospl
Tullamore
Tullamore
Geashill
Clonygowan
Na Cluainte
Tullamore College
Avondale Estate
Regional Hospital
Kilbeggan East
Kilbeggan East
Austin Friars St
Castle Street
Rochfortbridge
Tyrrellspass
Tyrrellspass
Rochfortbridge
Gainestown
Gainestown

Over time

Overall score across the last 21 checks — down 1.5 since 2026-10-21.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	87.5	first check
2026-10-03	87.3	down 0.2
2026-10-04	87.3	no change
2026-10-05	87.3	no change
2026-10-06	87.3	no change
2026-10-07	87.5	up 0.2
2026-10-08	87.3	down 0.2
2026-10-09	87.3	no change
2026-10-10	87.3	no change
2026-10-11	87.5	up 0.2
2026-10-12	87.2	down 0.3
2026-10-13	87.2	no change
2026-10-14	87.5	up 0.3
2026-10-15	87.3	down 0.2
2026-10-16	87.5	up 0.2
2026-10-17	87.2	down 0.3
2026-10-18	85.4	down 1.8
2026-10-19	85.4	no change
2026-10-20	87.2	up 1.8
2026-10-21	87.2	no change
2026-10-22	85.7	down 1.5

What changed since your last check

Correctness down 3.3
Freshness no change
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.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-22	`f2ae80148375`	2027-10-21	Current rubric: see the trend above
2026-10-20 to 2026-10-21 (2 checks)	`be7dfc60015c`	2027-10-19	Current rubric: see the trend above
2026-10-19	`f10314e5cb23`	2027-10-17	Current rubric: see the trend above
2026-10-18	`88b6c79340e1`	2027-10-17	Current rubric: see the trend above
2026-10-17	`d276b4da8576`	2027-10-16	Current rubric: see the trend above
2026-10-16	`41bcf72b9f25`	2027-10-15	Current rubric: see the trend above
2026-10-15	`987887803bb0`	2027-10-14	Current rubric: see the trend above
2026-10-14	`64aded316ea8`	2027-10-13	Current rubric: see the trend above
2026-10-13	`f08c1284e379`	2027-10-12	Current rubric: see the trend above
2026-10-12	`540a043e80bf`	2027-10-10	Current rubric: see the trend above
2026-10-11	`67c5dbb32fc3`	2027-10-10	Current rubric: see the trend above
2026-10-10	`6e2433952dab`	2027-10-09	Current rubric: see the trend above

Showing the 12 most recent of 81 periods.

What changed in this feed

Overall score fell 1.5 points since 2026-10-21.

The feed file was re-published since 2026-10-21 (-274 KB).

New since 2026-10-21 (1 finding)

Warning1 instance
Some service calendars in the feed have already ended.
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Changed counts

down 73 of 73 trips don't say whether the vehicle is wheelchair accessible. (127 → 73) (scorecard_wheelchair_accessible_unknown)
down Some rider-facing names are in ALL CAPS or all lowercase. (39 → 21) (mixed_case_recommended_field)

No longer reported since 2026-10-21 (1 finding)

Unsorted stop times (flagged by the MobilityData validator). (unsorted_stop_times)

This records the later feed state. It does not establish who made a change or why.

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

6 findings, ordered by severity.

Show every finding

Warning73 instances
73 of 73 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)
Warning21 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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning4 instances
4 of 107 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)
Warning1 instance
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.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · 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
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide for service_window_outside_feed_period · 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 96% 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 364 days.
Accessible Not yet: States wheelchair access on 96% 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 364 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 90 / 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 69 / 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 Ireland portfolio: the same scorecards for every feed we track in that group, on one free page.

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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/"><img src="https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/badge.svg" width="320" height="58" alt="Slieve Bloom Coach Tours: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Slieve Bloom Coach Tours: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/badge.svg)](https://gtfsscorecard.org/agency/slieve-bloom-coach-tours/)

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/slieve-bloom-coach-tours/2026-10-22.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-22. 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.

GTFS Scorecard. (2026). Slieve Bloom Coach Tours GTFS feed-quality record, dated 2026-10-22 (grade B (85.7/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 f2ae80148375…). https://gtfsscorecard.org/data/artifacts/slieve-bloom-coach-tours/2026-10-22.json

@misc{gtfsscorecard-slieve-bloom-coach-tours-2026-10-22,
  title        = {Slieve Bloom Coach Tours GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/slieve-bloom-coach-tours/2026-10-22.json}},
  note         = {Checked 2026-10-22; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (85.7/100)}
}

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