← All agencies

Feed status · checked 2026-10-16

Luas (Dublin light rail)

Based on the official feed source on file

Service mode Tram

FDCBA

76.5 / 100

down 0.6 since 2026-10-15

Cataloged in Dublin, Ireland.

Covers 55 daysAccessibility gapsRealtime not yet published

Source feed: https://www.transportforireland.ie/transitData/Data/GTFS_LUAS.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 3 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

Luas (Dublin light rail)’s published feed lists 2 tram / light rail routes, 2,935 scheduled trips and 128 stops. Its service dates run from 2026-10-15 through 2026-12-10. The published file last changed on 2026-10-16.

Top things to fix

Fix 01

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

125 of 128 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 125 of 128 stops, about 98% of them.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +24 points in its category

Fix 02

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

2935 of 2935 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.

Fixing this covers all 2,935 trips in the feed.

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

Fix 03

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

Agency: Luas (Dublin light rail)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 125 of 128 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/luas/?finding=scorecard_wheelchair_boarding_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_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 55 days.
Published accessibility data: Accessibility information is stated for 2.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 (Luas (Dublin light rail)) scored C (76.5 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 125 of 128 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 2935 of 2935 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/

3. 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/

Full scorecard: https://gtfsscorecard.org/agency/luas/

Score by category

Correctness90.0 / 100

The MobilityData validator flagged 4 kinds of issue across 1619 instances (0 error, 1388 warning, 231 informational).

Freshness91.7 / 100

Service data covers the next 55 days.

Rider experience45.6 / 100

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

Accessibility1.5 / 100

2% of stops state accessibility (0% 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 128 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.

Green (red)
Red (red)

Routes in Luas (Dublin light rail)'s feed
Route	Type	Line color
Green Parnell - Brides Glen	Tram / light rail	red
Red The Point - Tallaght	Tram / light rail	red

List every stop

Dawson
Marlborough
Trinity
St. Stephen's Green
St. Stephen's Green
Harcourt
Charlemont
Charlemont
Ranelagh
Ranelagh
Beechwood
Beechwood
Cowper
Cowper
Milltown
Milltown
Kylemore
Kylemore
Bluebell
Bluebell
Blackhorse
Blackhorse
Drimnagh
Drimnagh
Goldenbridge
Goldenbridge
Suir Road
Suir Road
Rialto
Rialto
Fatima
Fatima
James's
James's
Heuston
Heuston
Museum
Museum
Smithfield
Smithfield
Four Courts
Four Courts
Jervis
Jervis
Abbey St.
Abbey St.
Busáras
Busáras
Connolly
Connolly
George's Dock
George's Dock
Mayor Square
Mayor Square
Spencer Dock
Spencer Dock
The Point
The Point
Harcourt
Dawson
Westmoreland
O'Connell - GPO
Grangegorman
Phibsborough
Phibsborough
Broombridge
Broombridge
Dominick
Broadstone
Cabra
O'Connell Upr.
Parnell
Dominick
Grangegorman
Cabra
Broadstone
Cookstown
Cookstown
Hospital
Hospital
Tallaght
Tallaght
Belgard
Belgard
Kingswood
Kingswood
Red Cow
Red Cow
Fettercairn
Fettercairn
Cheeverstown
Cheeverstown
Citywest
Citywest
Fortunestown
Fortunestown
Saggart
Saggart
Windy Arbour
Windy Arbour
Dundrum
Dundrum
Balally
Balally
Sandyford
Sandyford
Kilmacud
Kilmacud
Stillorgan
Stillorgan
Central Park
Central Park
Glencairn
Glencairn
The Gallops
The Gallops
Leopardstown
Leopardstown
Ballyogan
Ballyogan
Carrickmines
Carrickmines
Laughanstown
Laughanstown
Cherrywood
Cherrywood
Brides Glen
Brides Glen

Over time

Overall score across the last 15 checks — down 0.6 since 2026-10-15.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	76.9	first check
2026-10-03	76.9	no change
2026-10-04	76.9	no change
2026-10-05	76.9	no change
2026-10-06	76.9	no change
2026-10-07	76.9	no change
2026-10-08	76.9	no change
2026-10-09	76.9	no change
2026-10-10	76.9	no change
2026-10-11	76.9	no change
2026-10-12	76.5	down 0.4
2026-10-13	76.0	down 0.5
2026-10-14	75.6	down 0.4
2026-10-15	77.1	up 1.5
2026-10-16	76.5	down 0.6

What changed since your last check

Correctness down 0.2
Freshness down 1.6
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-16	`4da666450988`	2026-12-10	Current rubric: see the trend above
2026-10-15	`1082d8540c25`	2026-12-10	Current rubric: see the trend above
2026-10-14	`322e16c7a31f`	2026-12-10	Current rubric: see the trend above
2026-10-13	`474e7525f0cb`	2026-12-10	Current rubric: see the trend above
2026-10-12	`6dc84d037241`	2026-12-10	Current rubric: see the trend above
2026-10-11	`af6a8d2b06eb`	2026-12-10	Current rubric: see the trend above
2026-10-10	`37a32a4cd1d1`	2026-12-10	Current rubric: see the trend above
2026-10-09	`6661fac439e9`	2026-12-10	Current rubric: see the trend above
2026-10-08	`30c690985e67`	2026-12-10	Current rubric: see the trend above
2026-10-07	`ea3687c9db0b`	2026-12-10	Current rubric: see the trend above
2026-10-06	`cb71f0768399`	2026-12-10	Current rubric: see the trend above
2026-10-05	`7d190c1dc50e`	2026-12-10	Current rubric: see the trend above

Showing the 12 most recent of 79 periods.

What changed in this feed

Overall score fell 0.6 points since 2026-10-15.

The feed file was re-published since 2026-10-15 (+11 KB).

Changed counts

up Unsorted stop times (flagged by the MobilityData validator). (21 → 228) (unsorted_stop_times)

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

Warning2935 instances
2935 of 2935 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)
Warning1388 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)
Warning125 instances
125 of 128 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
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)
Info228 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2 instances
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)
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.)
Finding code: feed_valid_beyond_total_service_window · 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 2% 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 55 days.
Accessible Not yet: States wheelchair access on 2% 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 55 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 92 / 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 46 / 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.

Similar feeds in Dublin

Other scorecards in Dublin, 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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/luas/"><img src="https://gtfsscorecard.org/agency/luas/badge.svg" width="320" height="58" alt="Luas (Dublin light rail): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Luas (Dublin light rail): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/luas/badge.svg)](https://gtfsscorecard.org/agency/luas/)

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/luas/2026-10-16.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-16. 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). Luas (Dublin light rail) GTFS feed-quality record, dated 2026-10-16 (grade C (76.5/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 4da666450988…). https://gtfsscorecard.org/data/artifacts/luas/2026-10-16.json

@misc{gtfsscorecard-luas-2026-10-16,
  title        = {Luas (Dublin light rail) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/luas/2026-10-16.json}},
  note         = {Checked 2026-10-16; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (76.5/100)}
}

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