← All agencies

Feed status · checked 2026-10-16

Tampere regional transport (Nysse)

Based on the official feed source on file

Service mode Tram + Bus

FDCBA

75.6 / 100

unchanged since 2026-10-15

Cataloged in Pirkanmaa, Finland.

Covers 86 daysAccessibility gapsRealtime not yet published

Source feed: http://data.itsfactory.fi/journeys/files/gtfs/latest/gtfs_tampere.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 10 days 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

Tampere regional transport (Nysse)’s published feed lists 105 routes (tram / light rail and bus), 80,812 scheduled trips and 3,429 stops. The published file last changed on 2026-10-05.

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

3429 of 3429 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 3,429 stops in the feed.

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

Fix 02

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Two fields, set once in export settings.worth about +15 points in its category

Fix 03

Check the flagged stop times for transposed minutes.

Some scheduled trips move faster between stops than a transit vehicle can. Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.

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.

⏱ A few minutes per flagged trip.worth about +8 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: Tampere regional transport (Nysse)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 3429 of 3429 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/tampere-nysse/?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_missing_feed_info_dates
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 fast_travel_between_consecutive_stops
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 86 days.
Published accessibility data: Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: Fare information is published using GTFS Fares v1.
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 (Tampere regional transport (Nysse)) scored C (75.6 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: 3429 of 3429 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. Add feed_info.txt with feed_start_date and feed_end_date to your export.
   What: feed_info.txt is missing its start/end dates (the file itself is absent)
   Finding code: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

3. Check the flagged stop times for transposed minutes.
   What: Some scheduled trips move faster between stops than a transit vehicle can.
   Finding code: fast_travel_between_consecutive_stops
   Guide: https://gtfsscorecard.org/fix/fast_travel_between_consecutive_stops/

Full scorecard: https://gtfsscorecard.org/agency/tampere-nysse/

Score by category

Correctness76.0 / 100

The MobilityData validator flagged 7 kinds of issue across 3703 instances (0 error, 1124 warning, 2579 informational).

Freshness85.0 / 100

Service data covers the next 86 days.

Rider experience67.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 published.

Accessibility37.5 / 100

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

FaresLegacy fares

Fares are applied to trips.

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

1 (red)
10 (teal)
101 (teal)
102 (teal)
104 (teal)
109 (teal)
11 (teal)
12 (teal)
13 (teal)
14 (teal)
15 (teal)
16 (teal)
17 (teal)
18 (teal)
2 (teal)
20 (teal)
21 (teal)
22 (teal)
23 (teal)
24 (teal)
26 (teal)
27 (teal)
28 (teal)
29A (teal)
29B (teal)
3 (red)
30 (teal)
301 (teal)
31 (teal)
32 (teal)
33 (teal)
34 (teal)
35 (teal)
36A (teal)
36B (teal)
39 (teal)
4 (teal)
40 (teal)
40A (teal)
40B (teal)
40C (teal)
41 (teal)
42 (teal)
43U (teal)
44 (teal)
44A (teal)
44B (teal)
45 (teal)
46 (teal)
47 (teal)
48 (teal)
48A (teal)
48B (teal)
48C (teal)
48D (teal)
49 (teal)
5 (teal)
50 (teal)
52A (teal)
52B (teal)
55 (teal)
56 (teal)
57 (teal)
59 (teal)
6 (teal)
60 (teal)
60U (teal)
63 (teal)
64 (teal)
65 (teal)
65A (teal)
66 (teal)
67 (teal)
68U (teal)
69U (teal)
7 (teal)
70 (teal)
71 (teal)
72 (teal)
77 (teal)
77X (teal)
78 (teal)
79 (teal)
80 (teal)
80Y (teal)
81 (teal)
82 (teal)
84 (teal)
85 (teal)
86 (teal)
86X (teal)
87U (teal)
8A (teal)
8B (teal)
90 (teal)
90A (teal)
91 (teal)
92 (teal)
93 (teal)
95 (teal)
96 (teal)
97A (teal)
97B (teal)
97C (teal)
97D (teal)

Routes in Tampere regional transport (Nysse)'s feed
Route	Type	Line color
1 Kaupin kampus - Keskustori - Lentävänniemi	Tram / light rail	red
10 Kaukajärvi - Keskustori - Tahmela	Bus	teal
101 Keskustori - Messukeskus	Bus	teal
102 Lielahti - Tesoma - Messukeskus	Bus	teal
104 Hervanta - Messukeskus	Bus	teal
109 Kaukajärvi - Annala - Hervanta	Bus	teal
11 Killo - Pere - Ratina - Petsamo	Bus	teal
12 Vaitti - Sorin aukio	Bus	teal
13 Lintyhytti - Ratina - Tays	Bus	teal
14 Tays Arvo - Turtola - Ratina - Särkänniemi	Bus	teal
15 Sorila - Linnainmaa - Kaupin kampus	Bus	teal
16 Takahuhti - Kaupin kampus	Bus	teal
17 Hervanta - Vehmainen - Linnainmaa - Kaupin kampus	Bus	teal
18 Atala - Linnainmaa - Kaupin kampus	Bus	teal
2 Rauhaniemi - Särkänniemi	Bus	teal
20 Keskustori - Lentävänniemi	Bus	teal
21 Hiedanranta - Ryydynpohja	Bus	teal
22 Hiedanranta - Siivikkala	Bus	teal
23 Lielahti - Reuharinniemi	Bus	teal
24 Lielahti - Lentävänniemi	Bus	teal
26 Rahola - Ranta-Kaarila - Ratina - Höytämö	Bus	teal
27 Järvensivu - Ratinanranta - Pispalanharju	Bus	teal
28 Multisilta - Ratinanranta - Myllypuro	Bus	teal
29A Ojala - Kyttälä - Lamminpää	Bus	teal
29B Ojala - Kyttälä - Pyynikintori	Bus	teal
3 Hervanta - Hakametsä - Sorin aukio	Tram / light rail	red
30 Kyösti - Pyynikintori	Bus	teal
301 Lintuhytti - Hervantajärvi	Bus	teal
31 Partola - Sarankulma - Keskustori	Bus	teal
32 Partola - Keskustori	Bus	teal
33 Mäyränmäki - TAKK - Keskustori	Bus	teal
34 Lielahti - Tesoma - Pirkkala	Bus	teal
35 Mäyränmäki - Keskustori	Bus	teal
36A Hervanta - Lahdesjärvi - Härmälä - Nuoliala - Pirkkala	Bus	teal
36B Hervanta - Lahdesjärvi - Härmälä - Linnakallio - Pirkkala	Bus	teal
39 Höökinmäki - Pirkkala - Sankila	Bus	teal
4 Länsi-Hervanta - Keskustori - Tesoma - Lielahti - Hiedanranta	Bus	teal
40 Kangasala - Tampere	Bus	teal
40A Pikonlinna - Kangasala - Keskustori	Bus	teal
40B Huutijärvi - Kangasala - Keskustori	Bus	teal
40C Kangasalan asema - Kangasala - Keskustori	Bus	teal
41 Huutijärvi - Kangasala - Kaupin kampus	Bus	teal
42 Kuhmoinen - Kuhmalahti - Sahalahti - Mobilia - Kangasala - Tampere Linja-autoasema	Bus	teal
43U Pälkäne - Kangasala - Tampere	Bus	teal
44 Kangasala - Valkeakoski	Bus	teal
44A Kangasala - Alanko - Valkeakoski	Bus	teal
44B Kangasala - Koulukampus - Valkeakoski	Bus	teal
45 Pikkola - Kangasala - Ruutana - Linnainmaa	Bus	teal
46 Pikkola - Kangasala - Suinula	Bus	teal
47 Kangasala - Orivesi	Bus	teal
48 Saarioinen - Sahalahti - Kangasala	Bus	teal
48A Pohja - Pakkala - Sahalahti - Kangasala - Pikkola	Bus	teal
48B Pohja - Kivisalmi - Pakkala - Sahalahti - Kangasala - Pikkola	Bus	teal
48C Pohja - Kuhmalahti - Pakkala - Sahalahti - Tiihala - Kangasala	Bus	teal
48D Pohja - Kuhmalahti - Kivisalmi - Pakkala - Sahalahti - Kangasala - Pikkola	Bus	teal
49 Orivesi - Eräjärvi - Pohja	Bus	teal
5 Länsi-Hervanta - Vuores - Keskustori	Bus	teal
50 Lempäälä - Ideapark - Tampere	Bus	teal
52A Haurala - Lempäälä - Vanattara - Keskustori	Bus	teal
52B Laasonportti - Lempäälä - Ruskea-ahde - Keskustori	Bus	teal
55 Vesilahti - Lempäälä - Tampere	Bus	teal
56 Lempäälä - Säijä	Bus	teal
57 Lempäälä - Mattila - Lempäälä	Bus	teal
59 Lempäälä - Ideapark - Lastunen - Lempäälä	Bus	teal
6 Vatiala - Linnainmaa - Sorin aukio	Bus	teal
60 Valkeakoski - Ideapark - Tampere	Bus	teal
60U Valkeakoski - Tampere	Bus	teal
63 Valkeakoski - Lempäälä	Bus	teal
64 Valkeakoski Tori - Sointula	Bus	teal
65 Valkeakosken kauppatori - Roukko - Eerola	Bus	teal
65A Valkeakosken kauppatori - Vääräkoivu - Eerola	Bus	teal
66 Valkeakoski, Linja-autoasema - Metsäkansa - Rantoo	Bus	teal
67 Valkeakoski tori - Ritvala	Bus	teal
68U Pälkäne - Uskila - Valkeakoski	Bus	teal
69U Akaa - Metsäkansa - Valkeakoski	Bus	teal
7 Linnainmaa - Keskustori - Tesoma	Bus	teal
70 Harjuniitty - Nokia - Tampere	Bus	teal
71 Tesoma - Kalkku - Ilkan alue - Nokia	Bus	teal
72 Keskustori - Nokia - Vihola - Sammalisto	Bus	teal
77 Nokia - Tottijärvi	Bus	teal
77X Nokia - Tottijärvi	Bus	teal
78 Nokia - Sarkola - Tottijärvi	Bus	teal
79 Ruskeepää - Koskenmäki - Nokia - Linnavuori - Siuro	Bus	teal
80 Moisio - Ylöjärvi - Vuorentausta - Tampere	Bus	teal
80Y Kauraslampi - Ylöjärvi - Vuorentausta - Tampere	Bus	teal
81 Asuntila - Ylöjärvi - Hiedanranta	Bus	teal
82 Metsäkylä - Ylöjärvi - Tampere	Bus	teal
84 Ylöjärvi - Takamaa - Lakiala	Bus	teal
85 Ylöjärvi - Mutala - Kyrönlahti - Kuru	Bus	teal
86 Siivikkala - Ylöjärvi	Bus	teal
86X Siivikkala - Ylöjärvi	Bus	teal
87U Ylöjärvi - Viljakkala - Kyrönlahti	Bus	teal
8A Levonmäki - Keskustori - Tesoma - Haukiluoma	Bus	teal
8B Hervanta - Kaipanen - Keskustori - Tesoma - Haukiluoma	Bus	teal
90 Terälahti - Maisansalo - Kämmenniemi - Sorila - Linja-autoasema	Bus	teal
90A Terälahti - Kämmenniemi - Sorila - Linnainmaa - Linja-autoasema	Bus	teal
91 Mäntylä - Terälahti - Kämmenniemi - Aitoniemi	Bus	teal
92 Kämmenniemi - Viitapohja	Bus	teal
93 Terälahti - Teiskon kirkkotie - Kämmenniemi	Bus	teal
95 Orivesi - Ruutana - Tampere linja-autoasema	Bus	teal
96 Oriveden terveysasema - Oriveden asema - Oriveden keskusta - Oripohja	Bus	teal
97A Virrat - Hirsilä - Orivesi	Bus	teal
97B Mänttä - Hirsilä - Orivesi	Bus	teal
97C Mänttä - Orivesi	Bus	teal
97D Mänttä - Savo - Orivesi	Bus	teal

List every stop

Keskustori H
Keskustori G
Keskustori K
Paloasema
Keskustori J
Keskustori I
Keskustori E
Keskustori F
Keskustori D
Metso
Aleksanterin kirkko
Pyynikintori C
Pyynikintori D
Pyynikintori E
Pyynikintori F
Keskustori C
Frenckell
Keskustori M
Keskustori L
Kaakinmaa
Satamakatu
Satamakatu
Kaakinmaa
Näsinpuisto
Hämeenpuisto
Näsinkallio
Näsinpuisto
Mustalahti
Mustanlahdenkatu
Mustanlahdenkatu
Amuri
Amuri
Särkänniemi C
Mariankatu
Mariankatu
Hämeenpuisto
Kortelahdenkatu
Kortelahdenkatu
Finlayson
Tuulensuu C
Tuulensuu D
Eteläpuisto
Eteläpuisto
Ratinanranta
Ratinanranta
Finlayson
Savilinna
Savilinna
Kyttälä
Kyttälä
Tammerinpuisto
Ratina
Ratina
Rautatieasema D
Rautatieasema E
Sorsapuisto
Sorsapuisto
Koskipuisto D
Koskipuisto C
Linja-autoasema L2
Linja-autoasema 3.laituri
Sorin aukio G
Sorin aukio F
Tampereen valtatie
Linja-autoasema saapuvat
Rautatieasema F
Linja-autoasema 4.-7.laiturit
Armonkallio
Armonkallio
Kastinsilta
Kastinsilta
Tammelankatu
Tammelantori
Tammelantori
Tapionkatu
Tapionkatu
Hotelli Kauppi
Osmonmäki
Osmonmäki
Juhlatalonkatu
Aleksanterinkatu
Pohjolankatu
Pohjolankatu
Yliopistonkatu
Tampere-talo
Tampere-talo
Yliopisto C
Yliopisto A
Yliopisto B
Yliopisto D
Sorin aukio C
Sorin aukio D
Sorin aukio E
Lapintie
Lapintie
Vapriikki
Vapriikki
Tietotalo
Juhlatalonkatu
Tampella
Tampella
Soukkapuisto
Soukkapuisto
Ranta-Tampella
Ranta-Tampella
Pyynikintori A
Pyynikintori B
Tuulensuu A
Tuulensuu B
Keskustori A
Keskustori B
Koskipuisto A
Koskipuisto B
Rautatieasema A
Rautatieasema B
Tulli A
Tulli B
Sammonaukio A
Sammonaukio B
Kaleva A
Kaleva B
Uintikeskus A
Uintikeskus B
Kalevanrinne A
Kalevanrinne B
Hakametsä A
Hakametsä B
Turtola A
Turtola B
Hallila A
Hallila B
Pohjois-Hervanta A
Pohjois-Hervanta B
Opiskelija A
Opiskelija B
Hervantakeskus A
Hervantakeskus B
Hervannan kampus A
Hervannan kampus B
Etelä-Hervanta A
Etelä-Hervanta B
Hervantajärvi A
Hervantajärvi B
Särkänniemi A
Särkänniemi B
Tikkutehdas A
Tikkutehdas B
Santalahti A
Santalahti B
Hiedanranta A
Hiedanranta B
Tehdas A
Tehdas B
Niemen kartano A
Niemen kartano B
Niemenranta A
Niemenranta B
Lentävänniemi A
Lentävänniemi B
Pyhällönpuisto A
Pyhällönpuisto B
Kalevan kirkko A
Kalevan kirkko B
Hippos A
Hippos B
TAYS A
TAYS B
Kaupin kampus A
Kaupin kampus B
Sorin aukio A
Sorin aukio B
Tikkutehdas
Hiedanranta C
Hiedanranta D
Santalahti
Tikkutehdas
Hiedanranta E
Hiedanranta F
Lielahti B
Lielahti A
Lielahti D
Lielahti C
Lielahden koulu
Lielahden koulu
Lentävänniemi C
Lielahti F
Matilda Niemen katu
Matilda Niemen katu
Halkoniemi
Halkoniemi
Jänislampi
Jänislampi
Lentävänniemi D
Pohtolankatu
Pohtolankatu
Vetikonkatu
Vetikonkatu
Federleynkatu
Federleynkatu
Parrukatu
Isoniemenkatu
Listakatu
Listakatu
Papusenkatu
Papusenkatu
Pohtola
Pohtola
Siivikkala
Vilheminkatu
Possila
Possila
Kukkolankatu
Kukkolankatu
Viholankuja
Viholankatu
Ritalankatu
Ritalankatu
Lintulampi
Lintulampi
Lintulamminkatu
Lintulamminkatu
Enqvistinkatu
Enqvistinkatu
Sellukatu
Harjuntausta
Niemenranta C
Ryydynpohja
Harjuntausta
Niemenranta D
Harjunsivu
Niemenkartano C
Lielahti E
Lielahti th L
Lielahti th I
Pekkolantie
Pekkolantie
Mettistöntie
Mettistöntie
Ilmarinjärventie
Ilmarinjärventie
Vihattulantie
Vihattulantie
Teivaalantie 50
Teivaalantie 41
Niemenrannanaukio
Niemenrannanaukio
Reuharinniemi
Airokatu
Airokatu
Nuoralahti
and 3179 more (see the full list on the map or in the GeoJSON)

Over time

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

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	75.6	first check
2026-10-03	75.6	no change
2026-10-04	75.6	no change
2026-10-05	75.6	no change
2026-10-06	75.6	no change
2026-10-07	75.6	no change
2026-10-08	75.6	no change
2026-10-09	75.6	no change
2026-10-10	75.6	no change
2026-10-11	75.6	no change
2026-10-12	75.6	no change
2026-10-13	75.6	no change
2026-10-14	75.6	no change
2026-10-15	75.6	no change
2026-10-16	75.6	no change

What changed since your last check

Correctness no change
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-05 to 2026-10-16 (12 checks)	`0cd08ff319ea`	2027-01-10	Current rubric: see the trend above
2026-10-02 to 2026-10-04 (3 checks)	`430ee0b89c8d`	2027-01-10	Current rubric: see the trend above
2026-09-29 to 2026-10-01 (3 checks)	`430ee0b89c8d`	2027-01-10	C, 75.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-28	`533c55d96926`	2027-01-10	C, 75.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-21 to 2026-09-27 (7 checks)	`1478c5ceac3e`	2027-01-10	C, 75.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-01 to 2026-09-20 (16 checks)	`a863f06bd4a3`	2026-12-20	C, 75.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-25 to 2026-08-31 (7 checks)	`13f5308cefe2`	2026-11-08	C, 75.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-21 to 2026-08-24 (4 checks)	`a929e9f40759`	2026-11-08	C, 73.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-12 to 2026-08-20 (9 checks)	`637321077c9c`	2026-11-08	C, 73.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-05 to 2026-08-11 (7 checks)	`2d7fbc88073a`	2026-10-18	C, 73.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-04	`9722a2191fc9`	2026-10-18	C, 73.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-27 to 2026-08-03 (8 checks)	`56fcb15a9064`	2026-11-08	C, 73.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

Showing the 12 most recent of 14 periods.

What changed in this feed

Overall grade and score held steady since 2026-10-15.

Same feed file as 2026-10-15; the published zip did not change.

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

10 findings, ordered by severity.

Show every finding

Warning3429 instances
3429 of 3429 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)
Warning1068 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning50 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.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning5 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2577 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle 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.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules 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 100% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 86 days.
Accessible Not yet: States wheelchair access on 0% of stops and 100% 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

5 of 3429 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 86 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 76 / 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 68 / 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 Finland 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/tampere-nysse/"><img src="https://gtfsscorecard.org/agency/tampere-nysse/badge.svg" width="320" height="58" alt="Tampere regional transport (Nysse): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Tampere regional transport (Nysse): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/tampere-nysse/badge.svg)](https://gtfsscorecard.org/agency/tampere-nysse/)

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/tampere-nysse/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). Tampere regional transport (Nysse) GTFS feed-quality record, dated 2026-10-16 (grade C (75.6/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 0cd08ff319ea…). https://gtfsscorecard.org/data/artifacts/tampere-nysse/2026-10-16.json

@misc{gtfsscorecard-tampere-nysse-2026-10-16,
  title        = {Tampere regional transport (Nysse) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/tampere-nysse/2026-10-16.json}},
  note         = {Checked 2026-10-16; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (75.6/100)}
}

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