Feed status · checked 2026-07-24
Nitelink (Dublin Bus)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Dublin, Ireland.
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
832 of 832 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
108 of 108 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 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.
⏱ A small file for most flat-fare systems.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 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. · 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 156 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 6 kinds of issue across 95 instances (0 error, 87 warning, 8 informational).
Service data covers the next 156 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
104 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Fairfield Rd", "S Great George's St", "Mount Tallant Ave", 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.
- 29n (green)
- 31n (green)
- 33n (green)
- 42n (green)
- 46n (green)
- 49n (green)
- 69n (green)
- 70n (green)
- 77n (green)
- 7n (green)
- 84n (green)
- 88n (green)
| Route | Type | Line color |
|---|---|---|
| 29n Dublin City South, D'Olier Street - Baldoyle, Warrenhouse Road | Bus | green |
| 31n Dublin City South, D'Olier Street - Howth, Outside Train Station | Bus | green |
| 33n Westmoreland Street - Balbriggan | Bus | green |
| 42n Dublin City South, D'Olier Street - Portmarnock, Strand Road (St.Anne's Estate) | Bus | green |
| 46n Dublin City South, D'Olier Street - Dundrum, Outside Luas Station | Bus | green |
| 49n D'Olier Street - Kilnamanagh | Bus | green |
| 69n Dublin City South, Westmoreland Street - Saggart, | Bus | green |
| 70n Westmoreland Street - Tyrrelstown | Bus | green |
| 77n D'Olier Street - Citywest | Bus | green |
| 7n Dublin City South, D'Olier Street - Dún Laoghaire-Rathdown, Woodbrook Golf Club | Bus | green |
| 84n Dublin City South, D'Olier Street - Charlesland Road (Seaborne View Apts) | Bus | green |
| 88n Dublin City South, Westmoreland Street - Ashbourne, Ashbourne Kelly's | Bus | green |
This feed has 832 stops.
List every stop
- North Road
- Parnell Square West
- Parnell Square West
- Dorset Street Lwr
- Drumcondra Stn
- Archbishop's House
- Botanic Ave
- Drumcondra Village
- Dalymount
- Phibsborough Luas
- Cabra Road
- Quarry Road
- Home Farm Rd East
- Ballymun Library
- Nursing Home
- McKee Rd N
- McKee Road
- Willow Park Road
- Glasnevin Park
- Willow Park Avenue
- Botanic Gardens
- Met Éireann
- Cremore Ave
- Glasilawn Road
- Ballygall Rd E
- Mountjoy Street
- Clune Road
- Western Way
- Broadstone
- Phibsborough Road
- Monck Place
- Doyle's Corner
- Munster Street
- Prospect Way
- Wayfinding Centre
- Fairfield Rd
- Whitehall Village
- Plunket College
- Iveragh Road
- Shantalla Br
- O'Connell St Upper
- O'Connell St Upper
- Irish Life
- Wellington Quay
- Westmoreland Street
- Westmoreland Street
- Aston Quay
- D'Olier Street
- D'Olier Street
- D'Olier Street
- D'Olier Street
- Townsend Street
- Lombard Street East
- Erne Street
- Pearse Sq
- Grnd Canal Quay
- Ringsend Road
- Ringsend Depot
- Ringsend Village
- Irishtown Rd
- Star of the Sea
- Farney Park
- Sandymount
- Tritonville Road
- Nassau Street
- Nassau Street
- Merrion Sq North
- Holles Street
- Mount Street Lower
- Mount Street Br
- Haddington Road
- Lansdowne Park
- Lansdowne Road
- American Embassy
- RDS Ballsbridge
- Merrion Road
- British Embassy
- Shrewsbury Park
- Merlyn Road
- Merrion View Avenue
- St Vincent's Hosp
- Herbert Avenue
- Merrion Gates
- Busáras
- Connolly Stn
- Summerhill Pd
- Ballybough Road
- Clonliffe Ave
- Five Lamps
- Newcomen Bridge
- North Strand FS
- Annesley Br Road
- Fairview
- Marino Mart
- Howth Road
- Copeland Grove
- Ashbrook
- Castle Grove
- Collins Avenue
- Killester Village
- The Demesne
- The Meadows
- Raheny
- Raheny Library
- Avondale Park
- Maywood
- Foxfield
- Lonsdale
- James Larkin Road
- Strand View
- All Saints Road
- Sybil Hill Avenue
- All Saints Park
- Raheny
- Copeland Avenue
- Mt Temple School
- Donnycarney Rd
- St Brigid's Church
- Raheny Station
- Raheny Road
- Grange Park Road
- Ardscoil La Salle
- Grange Road
- Ardara Avenue
- Holy Trinity Church
- Holy Trinity NS
- Grangemore Road
- Kildare Street
- Royal Hospital
- Donnybrook Village
- Victoria Avenue
- Donnybrook Stdm
- Donnybrook Dpot
- Teresian School
- RTÉ Studios
- Belfield Court
- Berkeley Road
- Berkeley Road
- Stephen's Grn E
- Leeson Street Lwr
- Adelaide Road
- Leeson Street Upr
- Sussex Road
- St Canice's GNS
- Richmond St South
- Grove Park
- Cathal Brugha Brrks
- Military Road
- Rathmines
- Swan Shop Cntr
- Rathmines Garda
- Gardiner St Lwr
- Deverell Place
- Parnell Street East
- Mountjoy Sq West
- Gardiner St Upr
- Elm Mt Rd
- Artane Cottages
- Artane Rnbt
- Mask Avenue
- Coolock Village
- Dunree Pk
- Newtown Ctgs
- Darndale Roundabout
- Clarehall SC
- S Great George's St
- Camden Street Lwr
- Kenilworth Park
- Mount Tallant Ave
- Whitton Road
- Terenure North
- Terenure South
- Westbourne Road
- Dolphin's Barn
- Rutland Avenue
- Crumlin Road
- Merchant's Quay
- Melrose Avenue
- Philipsburgh Ave
- Morroch Terrace
- Marino Institute
- Torlogh Parade
- Marino Church
- Griffith Ave E
- Prospect Hill N
- Plunkett Avenue
- Barry Ave
- Barry Road
- Kildonan Park
- Clearwater SC
- McKee Avenue
- McKee Ave N
- Casement Rd
- Finglas West
- Coláiste Íde
- Wellmount Dr
- Valeview Dr
- Berryfield Rd
- Farnham Drive
- Cloonlara Road
- Tolka Vly Pk
- Whitehall Church
- Nephin Road
- St Mary's Convent
- Baggot Road
- Ashtown Grove
- Kempton
- Ashtown Roundabout
- Clontarf Rd Stn
- Strandville Ave
- Saint Lawrence Road
- Seaview Ave
- Castle Ave
- Clontarf Bths
- Oultan Road
- Clontarf Village
- Vernon Court
- Clontarf Depot
- Clontarf Coast
- North Bull Island
- Dollymount Pk
- Doyles Lane
- The Oaks
- Rosecourt
- Cabra Road
- Skreen Road
- Old Racecourse
- Dame Street
- Cornmarket
- Thomas Street
- James's Street
- St James Hospital
- Mount Brown
- Old Kilmainham
- Inchicore Library
- Inchicore Village
- Tyrconnell Rd N
- Tyrconnell Park
- Oblate Ch
- Bluebell Rd
- Hollybrook House
- Grove Court
- Bluebell
- Concorde B Park
- Ailesbury Road
- Coombe Hospital
- Crumlin Coll
- Iveagh Gnds
- Raphoe Road
- Crumlin Hospl
- and 582 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
9 findings, ordered by severity.
Show every finding
- Warning832 instances
832 of 832 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)
- Warning108 instances
108 of 108 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)
- Warning85 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 (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
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.)
Validator rule: trip_coverage_not_active_for_next7_days · 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)
- Info6 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus 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.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: future_calendar · 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 156 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 156 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 82 / 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 45 / 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/dublin-bus-nitelink/2026-07-24.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-24. 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.