Feed status · checked 2026-11-21

Transfort – City of Fort Collins (Transfort)

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

Service mode Bus

68.9 / 100

down 0.4 since 2026-11-20

Cataloged in Colorado.

Covers 56 daysAccessibility gapsRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks ridetransfort.com, the address the Mobility Database lists for the record that replaced this one. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

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

436 of 436 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 436 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 fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

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

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Colorado 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-11-02.

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
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. 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. Self-check a feed before you publish.

  2. Fix 02 · Read the fix guide for scorecard_no_fare_data

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Fix 03 · 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. 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 56 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
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.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Transfort – City of Fort Collins (Transfort)’s published feed lists 19 bus routes, 10,687 scheduled trips and 436 stops. Its service dates run from 2026-08-17 through 2027-01-16. The published file last changed on 2026-11-09.

Score by category

Correctness77.2 / 100

The MobilityData validator flagged 5 kinds of issue across 10078 instances (0 error, 10071 warning, 7 informational).

Freshness93.3 / 100

Service data covers the next 56 days.

Rider experience37.6 / 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.

Accessibility37.5 / 100

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

1 accessibility depth signal

  • 401 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("HARMONY & HINSDALE", "HARMONY & MASON", "STANFORD & HORSETOOTH", and more).

    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.

This feed has 436 stops.

Skip to route and stop data

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.

  • 14 (yellow)
  • 16 (gray)
  • 18 (white)
  • 19 (yellow)
  • 2 (teal)
  • 3 (gray)
  • 31 (brown)
  • 5 (yellow)
  • 6 (purple)
  • 7 (red)
  • 8 (brown)
  • 81 (teal)
  • 9 (pink)
  • ADA (pink)
  • FHS (green)
  • FLEX (blue)
  • GOLD (yellow)
  • HORN (pink)
  • MAX (green)
Routes in Transfort – City of Fort Collins (Transfort)'s feed
RouteTypeLine color
14 ROUTE 14Busyellow
16 ROUTE 16Busgray
18 ROUTE 18Buswhite
19 ROUTE 19Busyellow
2 ROUTE 2Busteal
3 ROUTE 3Busgray
31 ROUTE 31Busbrown
5 ROUTE 5Busyellow
6 ROUTE 6Buspurple
7 ROUTE 7Busred
8 ROUTE 8Busbrown
81 ROUTE 81Busteal
9 ROUTE 9Buspink
ADA ADA SHUTTLEBuspink
FHS FOOTHILLS SHUTTLEBusgreen
FLEX FLEX ROUTEBusblue
GOLD GOLD ROUTEBusyellow
HORN THE HORNBuspink
MAX MAX ROUTEBusgreen
List every stop
  • PROSPECT & WHITCOMB
  • PROSPECT & SHEELY
  • HARMONY & COLLEGE
  • LAKE & MERIDIAN
  • LAKE & CENTER (LOT #573)
  • TAFT HILL & HORSETOOTH
  • TAFT HILL & DEVONSHIRE
  • TAFT HILL & FISCH
  • CENTRO & NORTH FRONTAGE
  • PLUM & H.E.S.
  • EQUINE CENTER
  • LOVELAND NORTH TRANSIT CENTER (NTC)
  • COFFMAN & 8TH (ROOSEVELT PARK)
  • WILLOX & COLLEGE
  • LAKE & STADIUM APARTMENTS
  • LAKE & WHITCOMB
  • LAKE & AGGIE VILLAGE
  • PROSPECT & BAY
  • PROSPECT & STOVER
  • PROSPECT & REMINGTON
  • PROSPECT & MAX GUIDEWAY
  • PROSPECT & CENTRE
  • LAKE & CANVAS STADIUM
  • LADY MOON & TIMBERWOOD
  • ROCK CREEK & LADY MOON
  • HARMONY & BOARDWALK (W OF)
  • HARMONY & LEMAY (W OF)
  • HARMONY & WHEATON (E OF)
  • HARMONY & DELANY
  • SWALLOW & COLLEGE
  • HARMONY & UC HEALTH HARMONY CAMPUS
  • ROCK CREEK & ZIEGLER
  • LADY MOON & ROCK CREEK
  • LADY MOON & HARMONY
  • HARMONY & ZIEGLER
  • HARMONY & CORBETT
  • HARMONY & SNOW MESA
  • HARMONY & TIMBERLINE (E OF)
  • HARMONY & TIMBERLINE (W OF)
  • HARMONY & INNOVATION
  • HARMONY & MCMURRY (W OF)
  • HARMONY & LEMAY
  • HARMONY & BOARDWALK
  • PROSPECT & PROSPECT PKWY
  • MIDPOINT & LARIMER COUNTY
  • MIDPOINT & PROSPECT PKWY
  • PROSPECT PKWY & MIDPOINT
  • ROCK CREEK & FOSSIL RIDGE HS
  • ZIEGLER & ROCK CREEK
  • PROSPECT & ACADEMY
  • PROSPECT & RIVERSIDE
  • PROSPECT & WELCH
  • PROSPECT & LAKE
  • STOVER & ELIZABETH
  • OLIVE & PETERSON
  • ELIZABETH & WHEDBEE
  • PROSPECT & STOVER
  • PROSPECT & ROBERTSON
  • PROSPECT & LEMAY
  • PROSPECT & WELCH
  • PROSPECT & RIVERSIDE
  • SHIELDS & TROUTMAN
  • SHIELDS & WABASH
  • SHIELDS & HORSETOOTH
  • SHIELDS & CASA GRANDE
  • SHIELDS & SWALLOW
  • SHIELDS & DRAKE
  • SHIELDS & CENTRE
  • SHIELDS & HILL POND
  • SHIELDS & STUART
  • SHIELDS & LAKE
  • COLLEGE & LAKE
  • SHIELDS & PROSPECT
  • SHIELDS & STUART
  • SHIELDS & SHIRE
  • SHIELDS & RAINTREE
  • SHIELDS & DRAKE
  • SHIELDS & ROCKY MOUNTAIN
  • SHIELDS & SWALLOW
  • SHIELDS & CASA GRANDE
  • SHIELDS & HORSETOOTH
  • SHIELDS & WABASH
  • PROSPECT & TAFT HILL
  • PROSPECT & FUQUA
  • PROSPECT & LARCH
  • PROSPECT & OVERLAND
  • OVERLAND & WELLS FARGO
  • COLLEGE & ELIZABETH
  • ELIZABETH & AZURO
  • ELIZABETH & TIMBER
  • ELIZABETH & GLENMOOR
  • ELIZABETH & SKYLINE
  • COLLEGE & LAUREL
  • PROSPECT & SHIELDS
  • PROSPECT & HEATHERIDGE
  • RAMS VILLAGE
  • CONSTITUTION & ELIZABETH
  • ELIZABETH & SKYLINE
  • ELIZABETH & GLENMOOR
  • ELIZABETH & TAFT HILL
  • ELIZABETH & TIMBER
  • ELIZABETH & OVERLAND
  • OVERLAND & GOLDEN CURRANT
  • PROSPECT & OVERLAND
  • PROSPECT & LARCH
  • PROSPECT & FUQUA
  • PROSPECT & TAFT HILL
  • PROSPECT & UNDERHILL
  • PROSPECT & HEATHERIDGE
  • PROSPECT & SHIELDS
  • OLIVE & REMINGTON
  • LEMAY & SWALLOW
  • LEMAY & OXFORD
  • LEMAY & DRAKE
  • LEMAY & STUART
  • LEMAY & PROSPECT
  • LEMAY & POUDRE VALLEY HOSPITAL
  • LEMAY & ELIZABETH
  • LEMAY & POUDRE RIVER DR
  • LEMAY & MAGNOLIA
  • JEFFERSON & LINDEN
  • LEMAY & WOODWARD
  • LEMAY & MULBERRY
  • LEMAY & PENNOCK
  • LEMAY & POUDRE VALLEY HOSPITAL
  • LEMAY & PROSPECT
  • LEMAY & STUART
  • LEMAY & COLUMBIA
  • LEMAY & DRAKE
  • HORSETOOTH & MEADOWLARK
  • HORSETOOTH & COLONY
  • HORSETOOTH & WINDMILL (W OF)
  • HORSETOOTH & SHIELDS
  • HORSETOOTH & SENECA
  • HORSETOOTH & DUNBAR
  • TAFT HILL & DRAKE
  • TAFT HILL & MANCHESTER
  • TAFT HILL & STUART
  • TAFT HILL & PROSPECT (S OF)
  • TAFT HILL & CLEARVIEW
  • MULBERRY & WASHINGTON
  • HARMONY & HINSDALE
  • TAFT HILL & ELIZABETH
  • TAFT HILL & PROSPECT
  • TAFT HILL & MANCHESTER
  • TAFT HILL & VALLEY FORGE
  • HORSETOOTH & MASON
  • COLLEGE & MULBERRY
  • DRAKE & STOVER
  • DRAKE & TULANE (W OF)
  • DRAKE & COLLEGE (WB)
  • DRAKE & MAX GUIDEWAY (WB)
  • DRAKE & CSU VET SCHOOL
  • DRAKE & RESEARCH
  • DRAKE & WORTHINGTON
  • DRAKE & DAVIDSON
  • CENTRE & BOTANICAL
  • CENTRE & BAY
  • CENTER & BAY
  • DRAKE & SHIELDS
  • DRAKE & DAVIDSON
  • DRAKE & WORTHINGTON
  • DRAKE & REDWING
  • DRAKE & MAX GUIDEWAY (EB)
  • DRAKE & COLLEGE (EB)
  • DRAKE & STANFORD
  • WILLOW & COLLEGE
  • LINDEN & BRIDGE
  • CONIFER & REDWOOD
  • BLUE SPRUCE & CONIFER
  • BLUE SPRUCE & BRISTLECONE
  • BLUE SPRUCE & BUTCH CASSIDY
  • WILLOX & BLUE SPRUCE
  • COLLEGE & WILLOX
  • POUDRE VALLEY MOBILE HOME PARK
  • COLLEGE & WILLOX (N OF)
  • COLLEGE & WILLOX (S OF)
  • COLLEGE & CONIFER
  • COLLEGE & ALPINE
  • COLLEGE & POUDRE RIVER TRAIL
  • COLLEGE & POUDRE RIVER TRAIL
  • COLLEGE & VINE
  • COLLEGE & CONIFER
  • COLLEGE & CONIFER (N OF)
  • COLLEGE & BRISTLECONE
  • WILLOX & BLUE SPRUCE
  • BLUE SPRUCE & BUTCH CASSIDY
  • BLUE SPRUCE & BRISTLECONE
  • BLUE SPRUCE & CONIFER
  • LINDEN & LINDEN CENTER
  • CHERRY & LOOMIS
  • WOOD & CHERRY
  • WOOD & ELM
  • VINE & WOOD
  • VINE & HANNA (W OF)
  • LINCOLN MIDDLE SCHOOL
  • LANCER & VINE (N OF)
  • VINE & TAFT HILL
  • HARMONY & MASON
  • VINE & IRISH
  • VINE & SUNSET
  • VINE & HOLLYWOOD
  • OVERLAND & VINE
  • OVERLAND & HIGH
  • LAPORTE & OVERLAND
  • LAPORTE & HOLLYWOOD
  • LAPORTE & SUNSET
  • LAPORTE & IMPALA
  • LAPORTE & GRANDVIEW
  • LAPORTE & BRYAN
  • LAPORTE & LYONS
  • LAPORTE & JAMITH
  • LAPORTE & SHIELDS
  • LAPORTE & WASHINGTON
  • LAPORTE & LOOMIS
  • LAPORTE & SHERWOOD
  • MAIN & 21ST
  • LINCOLN & 8TH
  • US 287 & 65TH
  • SWALLOW & STANFORD (E OF)
  • COLLEGE & TRILBY
  • COLLEGE & SKYWAY
  • COLLEGE & HARMONY (S OF)
  • COLLEGE & CAMERON
  • COLLEGE & TRILBY
  • US 287 & CARPENTER
  • CLEVELAND & 8TH
  • US 287 & 14TH
  • MAIN & 21ST
  • 65TH & US 287
  • SHIELDS & HARMONY
  • HARMONY & STARFLOWER
  • SHIELDS & ROLLAND MOORE
  • PROSPECT & MASON
  • HARMONY & STARFLOWER
  • SHIELDS & TROUTMAN
  • MERIDIAN & REC CENTER
  • MERIDIAN & UNIVERSITY
  • SWALLOW & CAMELOT
  • SWALLOW & LEMAY
  • SWALLOW & STOVER
  • DRAKE & TAFT HILL
  • DRAKE & CONSTITUTION
  • DRAKE & DUNBAR
  • DRAKE & RAINTREE
  • PLUM & SCOTT
  • HARMONY & MASON
  • SHIELDS & ELIZABETH
  • LAUREL & SHIELDS
  • LAUREL & WASHINGTON
  • and 186 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — down 0.4 since 2026-11-20.

2026-11-09: 70.62026-11-10: 70.62026-11-11: 70.62026-11-12: 70.62026-11-13: 70.62026-11-14: 70.62026-11-15: 70.62026-11-16: 70.62026-11-17: 70.62026-11-18: 70.12026-11-19: 69.72026-11-20: 69.32026-11-21: 68.9
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0970.6 first check
2026-11-1070.6 no change
2026-11-1170.6 no change
2026-11-1270.6 no change
2026-11-1370.6 no change
2026-11-1470.6 no change
2026-11-1570.6 no change
2026-11-1670.6 no change
2026-11-1770.6 no change
2026-11-1870.1 down 0.5
2026-11-1969.7 down 0.4
2026-11-2069.3 down 0.4
2026-11-2168.9 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.7
  • 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
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-21 (13 checks)24f1fd8aa9632027-01-16Current rubric: see the trend above
2026-07-25 to 2026-11-06 (100 checks)1765080d31332024-05-11F, 39.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-07-24 (9 checks)1765080d31332024-05-11F, 39.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)1765080d31332024-05-11F, 39.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed over time

On 2026-11-09 this feed started at grade C. On 2026-11-19 the grade moved from C to D. As of 2026-11-21 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-11-19 Grade went C to D.

Everything we checked

9 findings, ordered by severity.

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

  • Warning436 instances

    436 of 436 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)

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

  • Warning4 instances

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info432 instances

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

    Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)

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

    Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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)

How we measured this

Checked for changes 18 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.

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.5, validator 8.0.1.

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 56 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 10687 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 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 56 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 55 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. This resource supports agencies; it is not a scoring authority.

Correctness 77 / 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 93 / 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 38 / 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 Colorado portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Colorado

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

Transfort – City of Fort Collins (Transfort): GTFS feed quality grade D, 68.9 of 100, checked 2026-11-21. GTFS Scorecard.

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/transfort-city-of-fort-collins-transfort/2026-11-21.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-11-21. 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.