GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Azienda Trasporti Pubblici di Nuoro (ATP Nuoro)

Based on the feed this agency publishes

Service mode Bus

55.1 / 100

unchanged since 2026-07-18

Catalogued in Sardegna, Italy.

Covers 165 daysAccessibility gapsRealtime not yet published

Provincial bus network around Nuoro. The direct download is MobilityData's hosted mirror; the operator's own endpoint does not serve a fetchable archive.

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.

Checked for changes 5 hours ago; last changed 5 hours ago.

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

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

314 of 314 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

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

1974 of 1974 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

Fix 03

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

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.

  1. 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.

  2. 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.

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 165 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

Correctness61.2 / 100

The MobilityData validator flagged 8 kinds of issue across 4131 instances (0 error, 4122 warning, 9 informational).

Freshness85.0 / 100

Service data covers the next 165 days.

Rider experience22.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (9).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("VIA B. SASSARI 7/A").

    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.

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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1D (teal)
  • 1FND (teal)
  • 1FNS (red)
  • 1FSD (teal)
  • 1FSS (red)
  • 1S (red)
  • 2D (white)
  • 2DB (white)
  • 2DBE (white)
  • 2DE (white)
  • 2S (pink)
  • 2SB (pink)
  • 2SBE (pink)
  • 2SE (pink)
  • 3 (gray)
  • 6K (gray)
  • 6S (gray)
  • 7L (brown)
  • 7N (brown)
  • 8 (orange)
  • 8E (orange)
  • 9 (green)
Routes in Azienda Trasporti Pubblici di Nuoro (ATP Nuoro)'s feed
RouteTypeLine color
1D LINEA 1DBusteal
1FND LINEA 1D FERIALE NOTTURNOBusteal
1FNS LINEA 1S FERIALE NOTTURNOBusred
1FSD LINEA 1D FESTIVOBusteal
1FSS LINEA 1S FESTIVOBusred
1S LINEA 1SBusred
2D LINEA 2DBuswhite
2DB LINEA 2D BARRATOBuswhite
2DBE LINEA 2D BARRATO ESTIVOBuswhite
2DE LINEA 2D ESTIVOBuswhite
2S LINEA 2SBuspink
2SB LINEA 2S BARRATOBuspink
2SBE LINEA 2S BARRATO ESTIVOBuspink
2SE LINEA 2S ESTIVOBuspink
3 LINEA 3Busgray
6K LINEA 6 MUSEALE - KANDINSKIBusgray
6S LINEA 6 MUSEALE - SOLITUDINEBusgray
7L LINEA 7 NUORO LOLLOVE - LOLLOVEBusbrown
7N LINEA 7 NUORO LOLLOVE - NUOROBusbrown
8 LINEA 8 NUORO MONTE ORTOBENEBusorange
8E LINEA 8 NUORO MONTE ORTOBENE ESTIVOBusorange
9 LINEA 9 NUORO PRATOSARDOBusgreen

This feed has 314 stops.

List every stop
  • VIA MANNIRONI CAPOLINEA
  • VIA MANNIRONI 2
  • VIA TRIESTE 100
  • VIA TRIESTE FR. 79
  • VIA TRIESTE AGIP
  • VIA TRIESTE 28-30
  • VIA ASIAGO FR. 22
  • VIA ZARA 24
  • VIA TORRES FR. 23
  • VIA FRASCHE 29
  • VIA S.GIOVANNI FR. 33
  • VIA S.GIOVANNI 47
  • VIA LOLLOVE 158
  • VIA LOLLOVE 92
  • VIA PREDA 'E ISTRADA
  • VIA ZELIA 12
  • VIA BALLERO 63
  • VIA BALLERO CIMITERO
  • VIA SOLITUDINE FR. 20
  • VIA DELLA PIETRA
  • VIA PORRINO FR. 5
  • VIA PORRINO FR. 29
  • VIA MONNI FRONTE ANG. V. CAV. ZUDDAS
  • VIA MARONGIU
  • VIA DON BOSCO FR. 11
  • VIA BISCOLLAI 13-15
  • VIA MANNIRONI S.N.C. FRONTE PARR. S.FRANCESCO
  • VIA MANNIRONI FR. 79
  • VIA MANNIRONI FR. 177
  • VIA MANNIRONI CAPOLINEA
  • VIA MANNIRONI 33
  • VIA MANNIRONI ZONC. ROTATORIA INCR. VIA TRIESTE
  • VIA TRIESTE FR 98
  • VIA TRIESTE 83
  • VIA REDIPUGLIA 15
  • VIA SODDU
  • VIA ZARA FR. 24
  • VIA TORRES FR 23
  • VIA FRASCHE FR. 29
  • VIA S.GIOVANNI FR. 33
  • VIA S.GIOVANNI FR. 49
  • VIA DELLA PIETRA 27
  • VIA LOLLOVE FR. 92
  • VIA LOLLOVE 43
  • VIA LOLLOVE FR 8
  • VIA BALLERO 102
  • VIA BALLERO FR CIMITERO
  • VIA SOLITUDINE 20
  • VIA PORRINO 3
  • VIA PORRINO 27
  • VIA MONNI INCROCIO V.CAV.ZUDDAS
  • VIA MARONGIU
  • VIA DON BOSCO 11
  • VIA BISCOLLAI 10
  • VIA MANNIRONI 73
  • VIA MANNIRONI 79
  • VIA MANNIRONI 177
  • VIA MANZONI CAPOLINEA
  • VIA MANZONI 24
  • VIA DEMURTAS 4
  • VIA BRIGATA SASSARI FR. 7A
  • VIA BRIGATA SASSARI 18
  • VIA BRIGATA SASSARI 30
  • VIA STAZIONE 1
  • VIA REPUBBLICA FR. 1
  • VIA REPUBBLICA 16
  • VIA REPUBBLICA 96
  • VIA REPUBBLICA 142
  • VIA REPUBBLICA 158
  • VIA RESISTENZA 35
  • VIA RAGAZZI DEL '99 FR. 3
  • VIA RAGAZZI DEL '99 32
  • VIA RAGAZZI DEL '99 66
  • VIA TEMPIO FR. 13
  • VIA TEMPIO (MATERNA) 3
  • VIA MADDALENA 10
  • VIA MADDALENA 30-32
  • VIA COSTITUZIONE FR. 20
  • VIA COSTITUZIONE FR. 4
  • VIA COSTITUZIONE 17-19
  • VIA COSTITUZIONE 1
  • VIA AOSTA FR. 3
  • VIA SARDEGNA FR. 33
  • VIA MANZONI 2
  • VIA DANTE (POSTE) 20
  • VIA DANTE 21
  • VIA B. SASSARI 7/A
  • VIA BRIGATA SASSARI 23
  • VIA B. SASSARI FR. 28
  • VIA CIUSA ROMAGNA 11-13
  • VIA REPUBBLICA FR. 76
  • VIA REPUBBLICA FR. 144
  • VIA REPUBBLICA FR. 156
  • VIA RESISTENZA 35
  • VIA TEMPIO 80-82
  • VIA TEMPIO (MATERNA) FR. 3
  • VIA MADDALENA FR. 10
  • VIA MADDALENA FR. 30-32
  • VIA COSTITUZIONE 20
  • VIA COSTITUZIONE 25
  • VIA KANDINSKY FR. 4
  • VIA SARDEGNA 54
  • VIA SARDEGNA 35
  • VIA COSTITUZIONE
  • VIA COSTITUZIONE
  • VIA TRIDENTINA FR. '3-5
  • VIA MASTINO 10
  • VIA OGGIANO 38A
  • VIA OGGIANO 74
  • VIA MARTIRI 27
  • VIA MARTIRI FR. 136
  • VIA MARTIRI RETRO CHIESA FR. 70
  • VIA TOSCANA 1
  • VIA TOSCANA FR. 19
  • VIA VENETO FR. 19
  • VIA CATTE 104
  • VIA NENNI FR. 1
  • VIA MUGHINA 45
  • VIA MANZONI CAPOLINEA
  • VIA MARTIRI FR. 16
  • VIA TOSCANA FR. 41
  • VIA LAVORO 12-14
  • VIA CAMPANIA 6
  • VIA TRIDENTINA 3
  • VIA MASTINO 10
  • VIA MASTINO 47
  • VIA MASTINO S:N:C FRONTE INAIL
  • VIA ENRICO DE NICOLA 38
  • VIA ENRICO DE NICOLA 60-64
  • VIA ENRICO DE NICOLA 74-76
  • VIA SALVATORE ALLENDE
  • VIA B. CROCE 55
  • VIA B. CROCE 27-25
  • VIA MARTIRI 136
  • VIA MARTIRI 68
  • VIA PIEMONTE 86
  • VIA PIEMONTE 18
  • VIA VENETO 9
  • VIA CATTE 104
  • VIA CATTE 53
  • VIA CATTE 4
  • VIA CONVENTO 2
  • VIA SARDEGNA FR. 12
  • VIA TOSCANA 35
  • VIA LOMBARDIA FR. 44
  • VIA LAVORO 11
  • VIA CAMPANIA 7
  • PIAZZA VENETO 33
  • VIA GIOV. XXIII 17
  • VIA TOLA 3
  • VIA CIUSA FR. 1
  • VIA CIUSA FR. 36
  • VIA SOLITUDINE FR. 5 (6BIS)
  • VIA BIVIO SEDDA E ORTAI
  • VIA FONTE "MILIANU"
  • VIA BIVO FARCANA
  • VIA SOLOTTI
  • VIA SA CORRA CHERVINA 2
  • VIA PARCO (CHIESA)
  • VIA PARCO (CAPOLINEA)
  • VIA BAR RISTORANTE SU REDENTORE
  • VIA SA CORRA CHERVINA 1
  • VIA SA CORRA CHERVINA 2
  • VIA SOLOTTI
  • VIA BIVIO FARCANA
  • VIA FARCANA
  • VIA BIVIO FARCANA
  • VIA FONTE "MILIANU"
  • P.ZA V. EMANUELE 18
  • VIA VITT.EMANUELE 44
  • CORSO GARIBALDI FR. 5
  • VIA CIUSA 1
  • VIA CIUSA 36
  • VIA SOLITUDINE S.N.C.
  • VIA FUNTANA BUDDIA 26
  • VIA FUNTANA BUDDIA FR. 31
  • VIA A. MORO 50
  • VIA LA MALFA 57
  • VIA LA MALFA 21
  • VIA FUNTANA BUDDIA 36
  • VIA FUNTANA BUDDIA 46-48
  • VIA MIMOSE S.N.C.
  • VIA MIMOSE FR. 57
  • VIA OLEANDRI 68
  • VIA ANEMONI 21
  • VIA ANEMONI TREV. V DELLE GARDENIE E V. DELLE ROSE
  • VIA GINESTRE 49
  • VIA GINESTRE FR. 28
  • VIA ROSE 29
  • VIA PLATANI TRA V. DELLE ROSE E V. DELLE GINESTRE
  • VIA MURICHESSA FRONTE INCROCIO V. DEI PINI
  • VIA MURICHESSA 9
  • VIA MURICHESSA (CARCERE) S.N.C.
  • VIA DESSANAY FR. 7
  • VIA CONGIU PES 6
  • VIA BIASI FR. 40
  • VIA MEREU FR. 12
  • VIA RESISTENZA (FRONTE BRICO) 61
  • VIA RESISTENZA (POLIVALENTE) S.N.C.
  • VIA DON BOSCO (EUROSTOK) S.N.C.
  • VIA F. BUDDIA FR. 26
  • VIA F. BUDDIA 25
  • VIA MORO 67
  • VIA LA MALFA 64
  • VIA LA MALFA 16
  • VIA F. BUDDIA 61
  • VIA F. BUDDIA FR. 48-46
  • VIA MIMOSE 1
  • VIA MIMOSE 57
  • VIA GIGLI FR. 14
  • VIA OLEANDRI FR. 70
  • VIA ANEMONI FR. 21
  • VIA ANEMONI INCR. V. DELLE GARDENIE
  • VIA GINESTRE FR. 72
  • VIA GINESTRE FR. 100
  • VIA MURICHESSA 66-102
  • VIA MURICHESSA 22-26
  • VIA MURICHESSA ANG. V. DEI PINI
  • VIA MURICHESSA SU PINU FR. 9
  • VIA MURICHESSA CARCERE 26
  • VIA DESSANAY 5
  • VIA CONGIU PES FR. 6A
  • VIA NONNIS 37
  • VIA BIASI 86
  • VIA BIASI 28
  • VIA BIASI (VOLKSWAGEN) 6
  • VIA MURICHESSA (FRONTE URRAI) 10
  • VIA RESISTENZA 10
  • VIA RESISTENZA 18
  • VIA DON BOSCO S.N.C. INCR. V. RODARI
  • VIA MURICHESSA
  • SCUOLA ANAP 2
  • C.COMMERC. FR. 11 (ARST)
  • CONS.INDUST. S.N.C.
  • VIA EFISIO MAGNANI 4
  • VIA MAGNANI (SFERA) FR. 33
  • VIA MAGNANI (EUROSPIN) 44
  • VIA FABIAN MELE (B.TICINO) 22
  • VIA BELLISARIO (BESAN) 36
  • VIA PIETRINO GUISO PILO 83
  • (SDA) VIA PIETRINO GUISO PILO 23-21
  • MCTC VIA GUISO PILO 5
  • VIA (BELLISARIO) FR. 124
  • VIA FRANCESCO CORDA FR. 15
  • VIA FRANCESCO CORDA (C.EDILE) FR. 37
  • VIA BELLISARIO FR. 69
  • VIA BELLISARIO (PETRETTO) 72
  • VIA BELLISARIO (MARRONCOLOR)) FR. 93
  • VIA BELLISARIO (BENAGLIO) 104
  • VIA LIVIO MAURI (EXPERT) FR. 76
  • and 64 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 55.12026-07-19: 55.1
Show the numbers
CheckScoreChange
2026-07-1855.1 first check
2026-07-1955.1 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-18.

Same feed file as 2026-07-18; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

14 findings, ordered by severity.

Show every finding
  • Warning3691 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

  • Warning1974 instances

    1974 of 1974 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

  • Warning412 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning314 instances

    314 of 314 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

  • Warning11 instances

    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

  • Warning3 instances

    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.)

    Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning3 instances

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

  • 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.)

    Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    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.)

    Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • 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.)

    Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Info314 instances

    About 314 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info9 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

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 165 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 165 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 61 / 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 22 / 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.

Azienda Trasporti Pubblici di Nuoro (ATP Nuoro) GTFS data quality grade: F

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/atp-nuoro/2026-07-19.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-19. 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.