← All agencies

Feed status · checked 2026-10-07

TriMet, Portland Streetcar

Based on the feed source on file; publisher ownership is not verified

Service mode Tram + Rail + 2 more

FDCBA

90.7 / 100

unchanged since 2026-10-06

Cataloged in Oregon.

Covers 143 daysRealtime access needed

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 12 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

TriMet, Portland Streetcar’s published feed lists 81 routes (tram / light rail, rail, bus and aerial lift), 67,510 scheduled trips and 6,027 stops. Its service dates run from 2026-09-13 through 2027-02-27. The published file last changed on 2026-10-06.

Top things to fix

Fix 01

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

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.

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.

⏱ Often a bulk fix in your scheduling software.worth about +6 points in its category

Fix 02

Delete the empty calendars or set their service days.Likely your export tool

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.

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 in your scheduling software.worth about +6 points in its category

Fix 03

Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Same route and agency url (flagged by the MobilityData validator). See the linked rule for what this affects.

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.

⏱ Varies.worth about +4 points in its category

Riders and need behind these fixes

This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
Oregon as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

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: TriMet, Portland Streetcar
Finding: mixed_case_recommended_field
Feed evidence: Some rider-facing names are in ALL CAPS or all lowercase.
Why it matters: ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Requested change: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
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/trimet-portland-streetcar/?finding=mixed_case_recommended_field#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 mixed_case_recommended_field
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 service_has_no_active_day_of_the_week
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
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 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 v2.
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 (TriMet, Portland Streetcar) scored A (90.7 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
   What: Some rider-facing names are in ALL CAPS or all lowercase.
   Finding code: mixed_case_recommended_field
   Guide: https://gtfsscorecard.org/fix/mixed_case_recommended_field/

2. Delete the empty calendars or set their service days.
   What: Some service calendars have no days of the week switched on.
   Finding code: service_has_no_active_day_of_the_week
   Guide: https://gtfsscorecard.org/fix/service_has_no_active_day_of_the_week/

3. Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
   What: Same route and agency url (flagged by the MobilityData validator).
   Finding code: same_route_and_agency_url

Full scorecard: https://gtfsscorecard.org/agency/trimet-portland-streetcar/

Score by category

Correctness78.8 / 100

The MobilityData validator flagged 6 kinds of issue across 31 instances (0 error, 22 warning, 9 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.

FaresFares v2

Fares are applied to trips.

Realtime qualityNot yet measured

This agency publishes realtime, but the feed needs an access key we don't have 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 6027 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 (teal)
10 (teal)
MAX Blue Line (teal)
11 (teal)
12 (teal)
14 (teal)
15 (teal)
155 (teal)
156 (teal)
16 (teal)
17 (teal)
18 (teal)
19 (teal)
MAX Yellow Line (yellow)
NS (brown)
A (red)
B (blue)
FX2 (brown)
20 (teal)
MAX Green Line (green)
WES Commuter Rail (gray)
Portland Aerial Tram (gray)
21 (teal)
22 (teal)
23 (teal)
24 (teal)
25 (teal)
26 (teal)
287 (teal)
288 (teal)
29 (teal)
MAX Orange Line (orange)
291 (orange)
292 (red)
293 (yellow)
30 (teal)
31 (teal)
33 (teal)
34 (teal)
35 (teal)
4 (teal)
40 (teal)
43 (teal)
44 (teal)
45 (teal)
46 (teal)
47 (teal)
48 (teal)
51 (teal)
52 (teal)
53 (teal)
54 (teal)
55 (teal)
56 (teal)
57 (teal)
59 (teal)
6 (teal)
62 (teal)
63 (teal)
67 (teal)
70 (teal)
71 (teal)
72 (teal)
73 (teal)
74 (teal)
75 (teal)
76 (teal)
77 (teal)
78 (teal)
79 (teal)
8 (teal)
81 (teal)
84 (teal)
86 (teal)
87 (teal)
88 (teal)
9 (teal)
MAX Red Line (red)
94 (teal)
96 (teal)
97 (teal)

Routes in TriMet, Portland Streetcar's feed
Route	Type	Line color
1 Vermont	Bus	teal
10 Steele	Bus	teal
MAX Blue Line	Tram / light rail	teal
11 Rivergate/Marine Dr	Bus	teal
12 Barbur/Sandy Blvd	Bus	teal
14 Hawthorne/Foster	Bus	teal
15 Belmont/NW 23rd	Bus	teal
155 Sunnyside	Bus	teal
156 Mather Rd	Bus	teal
16 NW Front Ave	Bus	teal
17 Holgate/NE 33rd	Bus	teal
18 Hillside	Bus	teal
19 Glisan/Canyon Rd	Bus	teal
MAX Yellow Line	Tram / light rail	yellow
NS Portland Streetcar - NS Line	Tram / light rail	brown
A Portland Streetcar - A Loop	Tram / light rail	red
B Portland Streetcar - B Loop	Tram / light rail	blue
FX2 Division	Bus	brown
20 Burnside/Stark	Bus	teal
MAX Green Line	Tram / light rail	green
WES Commuter Rail	Rail	gray
Portland Aerial Tram	Aerial lift	gray
21 Sandy Blvd/223rd	Bus	teal
22 Parkrose	Bus	teal
23 San Rafael	Bus	teal
24 Fremont/NW 18th	Bus	teal
25 Glisan/Troutdale Rd	Bus	teal
26 Thurman/NW 18th	Bus	teal
287 Blue Eastside Bus	Bus	teal
288 Blue Westside Bus	Bus	teal
29 International Way	Bus	teal
MAX Orange Line	Tram / light rail	orange
291 Orange Bus	Bus	orange
292 Red Bus	Bus	red
293 Yellow Bus	Bus	yellow
30 Estacada	Bus	teal
31 Webster/Beavercreek	Bus	teal
33 McLoughlin/King Rd	Bus	teal
34 Oatfield/River Rd	Bus	teal
35 Macadam/Greeley	Bus	teal
4 Fessenden/Woodstock	Bus	teal
40 Tacoma/Swan Island	Bus	teal
43 Taylors Ferry/Marquam Hill	Bus	teal
44 Capitol Hwy/N Rosa Parks	Bus	teal
45 Garden Home/Arnold Creek	Bus	teal
46 North Hillsboro	Bus	teal
47 Main/Baseline	Bus	teal
48 Cornell	Bus	teal
51 Vista/Sunset Blvd	Bus	teal
52 Farmington/185th	Bus	teal
53 Arctic/Allen	Bus	teal
54 Beaverton-Hillsdale Hwy	Bus	teal
55 Hamilton	Bus	teal
56 Scholls Ferry/Marquam Hill	Bus	teal
57 TV Hwy/Forest Grove	Bus	teal
59 Walker/Park Way	Bus	teal
6 Martin Luther King Jr Blvd	Bus	teal
62 Murray Blvd	Bus	teal
63 Washington Park/SW 6th	Bus	teal
67 Bethany/158th	Bus	teal
70 Milwaukie Ave/12th	Bus	teal
71 60th Ave	Bus	teal
72 Killingsworth/82nd Ave	Bus	teal
73 122nd Ave	Bus	teal
74 162nd Ave	Bus	teal
75 Cesar Chavez/Lombard	Bus	teal
76 Hall/Greenburg	Bus	teal
77 Broadway/Halsey	Bus	teal
78 Denney/Kerr Pkwy	Bus	teal
79 Clackamas/Oregon City	Bus	teal
8 Jackson Park/NE 15th	Bus	teal
81 Kane/257th	Bus	teal
84 Powell Valley/Orient Dr	Bus	teal
86 148th Ave	Bus	teal
87 Airport Way/181st	Bus	teal
88 Hart/198th	Bus	teal
9 Powell Blvd	Bus	teal
MAX Red Line	Tram / light rail	red
94 Tigard/Sherwood	Bus	teal
96 Boones Ferry Rd	Bus	teal
97 Tualatin-Sherwood/Kruse Way	Bus	teal

List every stop

Abernethy & Barclay
SW Allen & Erickson
NE 3rd & E Main
5400 Block NE Dawson Creek
NE Evergreen & Brookwood
3100 Block NE Dawson Creek
SE 223rd & Stark
NE Cornell & 102nd
NE Cornell & Amberglen Pkwy
NE Cornell & Overlook Dr
NE Cornell & John Olsen Ave
NE Cornell & Aloclek
NE Cornell & Cornelius Pass
NE Cornell & Butler
NE Cornell & Walbridge
SW Cedar Hills & Fairfield
NE Cornell & Amberglen Pkwy
NE Cornell & Overlook Dr
NE Cornell & John Olsen Ave
NE Cornell & 102nd
NE Cornell & Aloclek
NE Cornell & 25th
NE Cornell & 48th
NE Cornell & Cornelius Pass
SW Cedar Hills & Fairfield
NE Cornell & Butler
NE Cornell & Walbridge
NE Cornell & Stucki
NE Century & Alder/Orenco Stn
10200 Block SW Park Way
NE Century & Carillion
NE Century & Orenco Max Stn
NE Century & Dogwood
NE Century & Orenco Ridge
E Main & SE 58th Ct
E Main & NE 53rd
E Main & NE 49th
E Main & SE 58th Ct
E Main & NE 53rd
E Main & NE 49th
NE Century & Campus Way
NE Century & Dogwood
NE Century & Deer Run
NE Dawson Creek & Brookwood
NE Shute Rd & Dawson Creek Dr
NW 31st & Guam
3300 Block NW Guam
NW Guam & 35th
3300 Block NW 35th
NW Kaiser & Snowlily Dr
NW Kaiser & Two Ponds Dr
NW Springville & Sickle Terrace
NW Springville & Joss
NW Springville & 173rd
NW Bethany & Cornell
NW Bethany & Bronson
NW Bethany & Oak Hills Dr
NW Bethany & Telshire Terrace
NW Bethany & Ridgetop Lane
NW Bethany & West Union
NW Bethany & Saint Andrews
NW Bethany & Mitchell
4700 Block NW Bethany
NW Bethany & Laidlaw
NW Bethany & Kaiser Rd
Pier Park
SW Allen & Erickson
SW Cedar Hills & Huntington
NW Springville & Sickle Terrace
NW Springville & 165th Terrace
NW Springville & 173rd
NW Kaiser & Westbrook
NW Kaiser & Graf St
NW Bethany & Wismer
NW Bethany & Laidlaw
4700 Block NW Bethany
NW Bethany & Claremont Dr
SW Cedar Hills & Huntington
NW Bethany & Saint Andrews
NW Bethany & West Union
NW Bethany & Ridgetop Lane
NW Bethany & Telshire Dr
NW Bethany & Oak Hills Dr
NW Bethany & Cornell
Goose Hollow/SW Jefferson St MAX Station
Goose Hollow/SW Jefferson St MAX Station
Washington Park MAX Station
Washington Park MAX Station
20700 Block NE Halsey
SW Merlo Rd & Merlo MAX Station
SW Baseline & Main
SW Cedar Hills & Jenkins
SW Murray & Nike
SW Murray & Nike
SE Sunnyside & 122nd
SE Sunnyside & 128th
SE Sunnyside & 128th
SE Sunnyside & 132nd
SE Sunnyside & 132nd
SW Cedar Hills & Jenkins
SE Sunnyside & 139th
SE Sunnyside & 140th
SE Sunnyside & 142nd
SE Sunnyside & 142nd
14600 Block SE 147th
SE Oregon Trail Dr & Hines
SE Lake & Freeman Way
NE Evergreen Pkwy & Stucki
NW Cedar Hills & Leahy
NE Century & Oelrich
NE Century & Oelrich
NE Century & Walbridge
SE Tualatin Valley Hwy & 44th
N Columbia & Terminal 5 Access Rd
N Columbia & Terminal 5 Access Rd
SW Farmington & 185th
SW Columbia & 18th
NW Glencoe & Cody Ct
SW Cedar Hills & Lynnridge
400 Block SW 257th
400 Block SW 257th
700 SW Campus Dr at Doernbecher
N Ivanhoe & Leavitt
SW Cedar Hills & Lynnridge
Tigard Transit Center
NE Alberta & 7th
22600 Block SE Hwy 224
22600 Block SE Hwy 224
SE 28th & Carlton
SW Cedar Hills & Park Way
SE Tualatin Valley Hwy & 30th
NE Cornell & Elam Young East
NE Cornell & Brookwood Pkwy
17600 Block NE Sandy
SE Foster & 63rd
NE Cornell & Brookwood Pkwy
2200 Block NE Griffin Oaks
SW Allen & Hall
SW Cedar Hills & Park Way
SE Sunnyside & 122nd
SE Mather & Cedar Park Dr
10500 Block SE Mather
SE Mather & Bliss
SE Mather & 116th Ct
SE Mather & 119th Ct
SW Cedar Hills & Walker
SE Mather & 122nd
SW Hart & Forest Drive
SE Sunnyside & Valley View Ter
SE Sunnyside & 119th
SE Oregon Trail Dr & 152nd
SW Cedar Hills & Walker
SE 152nd & Territory Dr
SE 152nd & Bollam Dr
SE 152nd & Morning Way
SE 152nd & Morning Way
13300 Block SE Hubbard
13300 Block SE Hubbard
SE Hubbard & 125th
SE Hubbard & 125th
SE 122nd & Mountain Sun Dr
SE 122nd & Mountain Sun Dr
SE 122nd & Echo Valley
SE 122nd & Echo Valley
SE 97th & Lawnfield
SE 97th & Talbert Dr
Jantzen Beach Main Stop
SW 170th & Timberland Dr
SW 170th & Timberland Dr
27500 Block SE Eagle Creek Rd
NE 15th & Edgefield
NE 15th & Edgefield
NE 15th & Prahl Pkwy
NE 15th & Prahl Pkwy
NW 23rd & Overton
1300 Block NE 25th
1200 Block NE 25th
SE Washington & 2nd
NW St Helens & Marina Way
PSU South/SW 6th & College MAX Stn
SE 152nd & Sedona Drive
MAX Station/Oregon Zoo
SW Allen & Hall
SE 17th & Spokane
SE King & Home
Kerr & Touchstone
SE Flavel & 92nd (MAX Stn)
SE 152nd & Ranger Dr
NE Sandy & 154th
SW Patton & Humphrey
NW Cornell & 169th Pl
2400 Block NW Westover
NE Sandy & 181st/Airport Way
NE Sandy & Airport Way/181st
NW Cornell & 169th Pl
SE McLoughlin & Glen Echo
McLoughlin & Gloucester
McLoughlin & River Rd
SE McLoughlin & Glen Echo
SE McLoughlin & W Gloucester
McLoughlin & W Arlington
SW Center & 125th
SW Center & 125th
SW Allen & Menlo
N Channel Ave & Anchor
N Channel Ave & Ballast
19300 Block McLoughlin
19300 Block McLoughlin
NE Weidler & 15th
N Channel Ave & Commerce
SW Hart & 149th
SW Hart & 149th
N Channel Ave & Dolphin
SW 170th & Division
SW Dosch & Patton
SE 82nd & Sunnybrook
Oregon City Transit Center
8300 Block SW Apple Way
SE Belmont & 51st
N Chautauqua & Washburne
8400 Block NE 33rd Dr
NE Sandy & 154th
NE Shaver & 141st
NW 35th & Yeon
NE Evergreen Pkwy & Venetian Dr
NE Evergreen Pkwy & Venetian Dr
N Chautauqua & Washburne
N Williams & Emerson
W Baseline & SW 185th
SW 45th & Vermont
400 Block Beavercreek Rd
N Chautauqua & Alaska
SE Milwaukie & Powell
2600 Block N Marine
SE 52nd & Woodstock
NE Evergreen & Evergreen Middle School
SE Woodstock & 51st
SE International Way & Criterion Ct
SE International Way & Criterion Ct
SW 5th & Hall
NE M L King & Morgan
SW Allen & 107th
SW Allen & Menlo
N Chautauqua & Willis
26300 Block SE Hwy 224
26300 Block SE Hwy 224
NE 92nd & Hill
SW Chestnut & Bertha
Salamo & Day Rd
Salamo & Barrington Dr
and 5777 more (see the full list on the map or in the GeoJSON)

Over time

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

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-06	90.7	first check
2026-10-07	90.7	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-06 to 2026-10-07 (2 checks)	`b83bf99ac875`	2027-02-27	Current rubric: see the trend above
2026-08-06 to 2026-08-07 (2 checks)	`8fa85dba38a2`	2026-11-28	C, 71.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-09 to 2026-07-10 (2 checks)	`7db3e3981718`	2026-11-28	C, 71.8 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-07-02 to 2026-07-08 (7 checks)	`d5b0ba95776d`	2026-11-28	C, 70 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-25 to 2026-07-01 (7 checks)	`d9c69dc934b9`	2026-11-28	C, 70 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-06-24 (6 checks)	`6b80a497f82b`	2026-11-28	C, 70.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

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

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

7 findings, ordered by severity.

Show every finding

Warning9 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)
Warning6 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.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide for service_has_no_active_day_of_the_week · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning4 instances
Same route and agency url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_route_and_agency_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Info6 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)
Info3 instances
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)

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Ready: Service data covers the next 143 days.
agency_id provided Ready: agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals your NTD ID (optional) Not checked yet: This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

shapes.txt covers your trips Ready: All 67510 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

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/trimet-portland-streetcar/mark.svg)](https://gtfsscorecard.org/agency/trimet-portland-streetcar/)

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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

A local transit-data support resource is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. This resource supports agencies; it is not a scoring authority.

Correctness 79 / 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. FTA NTD readiness also checks that the published feed is valid.
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. FTA NTD readiness also checks that the published feed is current.
Rider experience 100 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Access needed to measure: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Oregon portfolio: the same scorecards for every feed we track in that group, on one free page.

For programs that support several agencies

This scorecard and the board one-pager for TriMet, Portland Streetcar are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.

The report for TriMet, Portland Streetcar uses the same numbers as this page: grade A (90.7 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.

One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.

See the program report bundle

See a sample bundle report: a real agency's current grade, with placeholder branding.

A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.

Similar feeds in Oregon

Other scorecards in Oregon, 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/trimet-portland-streetcar/"><img src="https://gtfsscorecard.org/agency/trimet-portland-streetcar/badge.svg" width="320" height="58" alt="TriMet, Portland Streetcar: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![TriMet, Portland Streetcar: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/trimet-portland-streetcar/badge.svg)](https://gtfsscorecard.org/agency/trimet-portland-streetcar/)

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/trimet-portland-streetcar/2026-10-07.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-07. 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). TriMet, Portland Streetcar GTFS feed-quality record, dated 2026-10-07 (grade A (90.7/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 b83bf99ac875…). https://gtfsscorecard.org/data/artifacts/trimet-portland-streetcar/2026-10-07.json

@misc{gtfsscorecard-trimet-portland-streetcar-2026-10-07,
  title        = {TriMet, Portland Streetcar GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/trimet-portland-streetcar/2026-10-07.json}},
  note         = {Checked 2026-10-07; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade A (90.7/100)}
}

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