GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Interurban Trolley

Based on the feed this agency publishes

Service mode Bus

85.2 / 100

unchanged since 2026-07-31

Catalogued in Indiana.

Covers 152 daysAccessibility gapsRealtime not yet published

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

Checked for changes 16 hours ago; last fetch returned HTTP 404.

Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: provisional.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.

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

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

399 of 399 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

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

Fix 02

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool

Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

⏱ Usually one export setting.worth about +6 points in its category

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.

Feed evidence
399 of 399 stops don't say whether a wheelchair user can board there.
Next action
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.
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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

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

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

  2. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide

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

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

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide

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

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

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 152 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 93.5% 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.

Score by category

Correctness84.8 / 100

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

Freshness100.0 / 100

Service data covers the next 152 days.

Rider experience74.0 / 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.

Accessibility35.1 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (35, 32, 30).

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

  • 348 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("15th & College (in)", "15th & College (out)", "24th & Mishawaka Ave.", 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.

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

  • 32 (green)
  • 33 (teal)
  • 50 (red)
  • 30 (orange)
  • 35 (orange)
  • KABS (teal)
Routes in Interurban Trolley's feed
RouteTypeLine color
32 Green WestBusgreen
33 Blue North PointeBusteal
50 Red Elkhart / GoshenBusred
30 South Bend / Mishawaka / ElkhartBusorange
35 Elkhart EastBusorange
KABS Lake City LoopBusteal
List every stop
  • Franklin & Second
  • Mishawaka Rd & Minuteman Way - Concord High School
  • Elkhart & Arlene
  • Meijer's Driveway & US 33
  • Meijer in Dunlap
  • Kohl's Dunlap
  • Walmart Dunlap (out)
  • Parkside Elementary
  • Greencroft (out)
  • Eisenhower South & Messick
  • Walmart Goshen
  • Eisenhower Dr South & Messick D
  • Greencroft (in)
  • Franklin & Main
  • Walmart Dunlap (In)
  • Meijer's Entrance & Main
  • Lincoln & Arlene
  • Mishawaka Rd & Minuteman Way - Martin's/Goodwill
  • Franklin & 6th
  • Indiana & Okama
  • Indiana & Nappanee
  • Nappanee & Vermont
  • Nappanee & Lexington
  • Nappanee & Strong
  • Nappanee & Bypass
  • CR 3 & California
  • Holiday Village
  • Elkhart Plaza West
  • Bristol & CR 10
  • Bristol & Oak
  • Bristol & Edwardsburg
  • Michigan & Bristol
  • Michigan & Randolph
  • Michigan & Beardsley
  • Michigan & Bower
  • Clyde & Sherman & Clyde
  • 3rd & Jefferson
  • High & 2nd
  • Marion & 5th
  • Marion & 8th
  • Oakland & Marion
  • Lincoln Center
  • Oakland & Indiana
  • Oakland & Cleveland
  • Oakland & Hubbard
  • Oakland & Lusher
  • Oakland & Stratford Commons
  • Stratford Commons
  • Oakland & CR 19
  • Mishawaka & Oakland
  • Mishawaka & 10th
  • Old Farm Apartments
  • Benham & Mishawaka
  • Hively & Benham
  • Prairie & Hively - Excel Center
  • Kroger
  • Benham & Thorndale
  • Lusher & 6th
  • 6th & Hubbard
  • 6th & Cleveland
  • Rosedale Apartments
  • 6th & Wagner
  • Faith Mission
  • Lexington & Meisner
  • Waterfall & High
  • Waterfall & Prairie
  • Richmond & Middlebury
  • Richmond & Williams
  • Sterling & Indiana
  • Prairie & Indiana
  • Prairie & Wolf
  • Prairie & Carlton
  • Pleasant Plain & Hively
  • Ivy Tech
  • Middleton Run & Toledo
  • Middleton Run & Magnum
  • Middlebury & Middleton Run
  • Middlebury & Collins
  • Middlebury & Graywood
  • Middlebury & Industrial
  • Middlebury & Riverview
  • Simpson & Middlebury
  • Simpson & Rice
  • Simpson & Superior
  • Superior & Bank
  • Superior & Goshen
  • Jackson & Goshen
  • Jackson & Corona
  • CR 6 & Cassopolis
  • Osolo & CR 6
  • Osolo & Dunny
  • Bristol & Johnson
  • Bristol & Independence
  • CR 6 & Park 6 Drive
  • Bristol & Adams
  • CR 6 & Johnson
  • Menards on Windsor
  • Riverside Apartments
  • CR 6 & Higgins
  • Clark & Jackson - Elkhart Aquatics Center
  • Osolo & Woodland Estates
  • Windsor & Cassopolis
  • Howard & Beardsley
  • Elkhart & Jackson
  • Osolo & Autumn Ridge
  • Johnson & Baldwin
  • Maple Lane Apartments
  • Bristol & Baldwin
  • Osolo & Bristol
  • Cassopolis & Windsor
  • Cassopolis & Woodlawn
  • David & Plaza
  • Beardsley & Cassopolis
  • CR 4 & Cassopolis
  • Walmart at CR 6
  • Rogers & Johnson
  • Northview & North Pointe
  • Cassopolis & South
  • Cassopolis & Baldwin
  • Emerson & Cassopolis
  • North Lake Apartments
  • Cassopolis & Orange
  • Martin's at North Pointe
  • Northpointe & Northview
  • Cassopolis & CR 6
  • Cassopolis & Country Club
  • Cassopolis & Simonton
  • Cassopolis & Sunset
  • Old US 20 & CR 1
  • Ash & Vistula
  • Oakland & Lincolnway
  • Lincolnway & Virginia
  • Lincolnway & Victoria
  • Byrkit & Lincolnway
  • Lincolnway & Mason - Mishawaka High School
  • Church & 3rd St
  • Mishawaka Transfer Station
  • Church & 3rd
  • Mishawaka High School - Lincolnway & Mason
  • Birkin & Lincolnway
  • Victoria & Lincolnway
  • Lincolnway & Bosse
  • Charles & Lincolnway
  • Lincolnway & Oakland Ave
  • Ash & Indiana
  • Cleveland Township Office
  • Lexington & West
  • Main St & E. 3rd St.
  • Meijer in Elkhart
  • Twin Branch Park - Lincolnway & Ballard
  • 15th & College (in)
  • 15th & College (out)
  • Ash & Beatrice (out)
  • Ash & Beatrice (in)
  • Ash & Glenwood (out)
  • Ash & Glenwood (in)
  • Benham & Chapman (in)
  • Benham & Chapman (out)
  • Benham & Cleveland (in)
  • Benham & Cleveland (out)
  • Benham & Dr MLK (in)
  • Benham & Dr MLK (out)
  • Benham & Hubbard (in)
  • Benham & Hubbard (out)
  • Benham & Indiana (in)
  • Benham & Indiana (out)
  • California & Nappanee (out)
  • College & 12th (in)
  • College & 12th (out)
  • College & Main (in)
  • College & Main (out)
  • Dunlap Meijer (in)
  • Eisenhower & 15th (in)
  • Eisenhower & 15th (out)
  • Eisenhower & Dierdorff (in)
  • Eisenhower & Dierdorff (out)
  • Eisenhower & Lincolnway (in)
  • Eisenhower & Lincolnway (out)
  • Eisenhower South & Dierdorff (in)
  • Eisenhower South & Dierdorff (out)
  • Eisenhower South & Industrial Park (in)
  • Eisenhower South & Industrial Park (out)
  • Elkhart & Bashor (in)
  • Elkhart & Bashor (out)
  • Elkhart & Green (in)
  • Elkhart & Green (out)
  • Elkhart & Peddlers Village
  • Elkhart & Reith (in)
  • Elkhart & Reith (out)
  • Elkhart & Riverside (in)
  • Elkhart & Riverside (out)
  • Elkhart & Southfield (in)
  • Elkhart & Southfield (out)
  • Elkhart General Hospital (out)
  • Elkhart General Hospital (in)
  • Franklin & Bridge (out)
  • Franklin & Bridge (in)
  • Franklin & Oakland (out)
  • Franklin & Oakland (in)
  • Goshen Library (in)
  • Goshen Library (out)
  • Heart's Desire (in)
  • Heart's Desire (out)
  • Lexington & 3rd (Green)
  • Lexington & Haines (out)
  • Lexington & Haines (in)
  • Lexington & Nappanee (out)
  • Elkhart Clinic - Lexington & Nappanee
  • Lexington & Nappanee (in)
  • Lexington Industrial Park (out)
  • Lexington Industrial Park (in)
  • Lincoln & 2nd (in)
  • Lincoln & 2nd (out)
  • Lincoln & Chicago (in)
  • Lincoln & Chicago (out)
  • Lincoln & Main (in)
  • Lincoln & Main (out)
  • Lincolnway & Ash (out)
  • Lincolnway & Ash (in)
  • Lincolnway & Beech (out)
  • Lincolnway & Beiger (out)
  • Lincolnway & Beiger (in)
  • Lincolnway & Bittersweet (in)
  • Lincolnway & Bittersweet (out)
  • Lincolnway & Brook (out)
  • Lincolnway & Brook (in)
  • Lincolnway & Capital (out)
  • Lincolnway & Capital (in)
  • Lincolnway & Chestnut (out)
  • Lincolnway & Chestnut (in)
  • Lincolnway & DeLorenzi (out)
  • Lincolnway & DeLorenzi (in)
  • Lincolnway & Erie (out)
  • Lincolnway & Erie (in)
  • Lincolnway & Guernsey (out)
  • Lincolnway & Guernsey (in)
  • Lincolnway & Laurel (out)
  • Lincolnway & Laurel (in)
  • Lincolnway & Mariellen (out)
  • Lincolnway & Mariellen (in)
  • Lincolnway & Merrifield (out)
  • Lincolnway & Merrifield (in)
  • Lincolnway & Orange (out)
  • Lincolnway & Orange (in)
  • Lincolnway & Oregon (out)
  • Lincolnway & Oregon (in)
  • Lincolnway & Peony (out)
  • Lincolnway & Peony (in)
  • Lincolnway & Pine (out)
  • Lincolnway & Pine (in)
  • and 149 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 85.22026-07-30: 85.22026-07-31: 85.22026-08-01: 85.2
Show the numbers
CheckScoreChange
2026-07-2585.2 first check
2026-07-3085.2 no change
2026-07-3185.2 no change
2026-08-0185.2 no change

What changed since your last check

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

What changed in this feed

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

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

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

Everything we checked

7 findings, ordered by severity.

Show every finding
  • Warning399 instances

    399 of 399 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 · See GTFS Schedule reference

  • Warning21 instances

    21 of 324 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning10 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    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 · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus 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 · See MobilityData GTFS Validator rules

  • Info6 instances

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    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 · See MobilityData GTFS Validator rules

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 152 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 324 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

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 94% of trips; the mark needs 90% of each.

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

  • 1 of 399 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 152 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.

Correctness 85 / 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 74 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Interurban Trolley GTFS data quality grade: B

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/interurban-trolley/2026-08-01.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-08-01. 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.