← All agencies

Feed status · checked 2026-10-22

Fertagus

Based on the official feed source on file

Service mode Rail

FDCBA

95.1 / 100

unchanged since 2026-10-21

Cataloged in Setúbal, Portugal.

Covers 143 daysRealtime not yet published

Source feed: https://www.fertagus.pt/GTFSTMLzip/Fertagus_GTFS.zip

One suburban-rail feed crossing the Lisboa and Setúbal districts. It is filed under the operator's Setúbal base and counted as one feed record.

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 67 minutes ago; last changed 34 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

Fertagus’s published feed lists 3 rail routes, 260 scheduled trips and 14 stops. Its service dates run from 2026-09-14 through 2027-03-14. The published file last changed on 2026-09-18.

Top things to fix

Fix 01

Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool

Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

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.

⏱ Usually an export-tool fix, not hand editing.worth about +6 points in its category

Fix 02

Turn on 'remove unused shapes' (or the like) in your export tool.Likely your export tool

The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.

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.

⏱ One setting.worth about +4 points in its category

Fix 03

Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

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.

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 quick look at the flagged files.

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: Fertagus
Finding: stop_too_far_from_shape_using_user_distance
Feed evidence: Some stops sit far from the route line, going by the feed's own distance values.
Why it matters: Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Requested change: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
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/fertagus/?finding=stop_too_far_from_shape_using_user_distance#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 stop_too_far_from_shape_using_user_distance
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.
Fix 02 · Read the fix guide for unused_shape
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.
Fix 03 · Read the fix guide for unknown_column
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 143 days.
Published accessibility data: Accessibility information is stated for 100% 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 (Fertagus) scored A (95.1 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
   What: Some stops sit far from the route line, going by the feed's own distance values.
   Finding code: stop_too_far_from_shape_using_user_distance
   Guide: https://gtfsscorecard.org/fix/stop_too_far_from_shape_using_user_distance/

2. Turn on 'remove unused shapes' (or the like) in your export tool.
   What: The feed contains route shapes no trip uses.
   Finding code: unused_shape
   Guide: https://gtfsscorecard.org/fix/unused_shape/

3. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
   What: Some files contain columns that are not part of the GTFS spec.
   Finding code: unknown_column
   Guide: https://gtfsscorecard.org/fix/unknown_column/

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

Score by category

Correctness88.8 / 100

The MobilityData validator flagged 4 kinds of issue across 47 instances (0 error, 34 warning, 13 informational).

Freshness100.0 / 100

Service data covers the next 143 days.

Rider experience100.0 / 100

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

Accessibility100 / 100

100% of stops state accessibility (100% 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 14 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.

Fertagus (red)
Fertagus (red)

Routes in Fertagus's feed
Route	Type	Line color
Fertagus Lisboa - Setúbal	Rail	red
Fertagus Lisboa - Coina	Rail	red
Fertagus Lisboa - Fogueteiro	Rail	red (no shape in feed)

List every stop

Fogueteiro
Penalva
Pinhal Novo
Venda do Alcaide
Palmela
Setúbal
Foros de Amora
Corroios
Pragal
Campolide
Sete-Rios
Entrecampos
Roma-Areeiro
Coina

Over time

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

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	95.1	first check
2026-10-03	95.1	no change
2026-10-04	95.1	no change
2026-10-05	95.1	no change
2026-10-06	95.1	no change
2026-10-07	95.1	no change
2026-10-08	95.1	no change
2026-10-09	95.1	no change
2026-10-10	95.1	no change
2026-10-11	95.1	no change
2026-10-12	95.1	no change
2026-10-13	95.1	no change
2026-10-14	95.1	no change
2026-10-15	95.1	no change
2026-10-16	95.1	no change
2026-10-17	95.1	no change
2026-10-18	95.1	no change
2026-10-19	95.1	no change
2026-10-20	95.1	no change
2026-10-21	95.1	no change
2026-10-22	95.1	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-02 to 2026-10-22 (21 checks)	`3e82db7a4e04`	2027-03-14	Current rubric: see the trend above
2026-09-18 to 2026-10-01 (14 checks)	`3e82db7a4e04`	2027-03-14	A, 95.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-09-13 (51 checks)	`8d83271fa890`	2027-01-07	A, 95.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-24	`8d83271fa890`	2027-01-07	A, 95.1 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

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

Same feed file as 2026-10-21; 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

4 findings, ordered by severity.

Show every finding

Warning32 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info12 instances
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)

Conformance mark Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.

[![GTFS conformance mark](https://gtfsscorecard.org/data/artifacts/fertagus/mark.svg)](https://gtfsscorecard.org/agency/fertagus/)

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 143 days.
Accessible Met: States wheelchair access on 100% of stops and 100% of trips.

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 143 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 89 / 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 100 / 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 Portugal portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Setúbal

Other scorecards in Setúbal, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Metro Sul do Tejo

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/fertagus/"><img src="https://gtfsscorecard.org/agency/fertagus/badge.svg" width="320" height="58" alt="Fertagus: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Fertagus: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/fertagus/badge.svg)](https://gtfsscorecard.org/agency/fertagus/)

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/fertagus/2026-10-22.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-10-22. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Fertagus GTFS feed-quality record, dated 2026-10-22 (grade A (95.1/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 3e82db7a4e04…). https://gtfsscorecard.org/data/artifacts/fertagus/2026-10-22.json

@misc{gtfsscorecard-fertagus-2026-10-22,
  title        = {Fertagus GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/fertagus/2026-10-22.json}},
  note         = {Checked 2026-10-22; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade A (95.1/100)}
}

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