← All agencies

Feed status · checked 2026-08-01

Bloomington Transit

Based on the feed this agency publishes

Service mode Bus

76.2 / 100

unchanged since 2026-07-31

Catalogued in Indiana.

Covers 363 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 80 minutes ago; last changed 34 hours ago.

Measured 3 of 4 score categories from the agency's own feed.

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 agency's own URL.

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

467 of 467 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

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

1000 of 1000 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

Check the flagged stop times for transposed minutes.

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

⏱ A few minutes per flagged trip.worth about +8 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
467 of 467 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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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. Check the flagged stop times for transposed minutes. · 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 363 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% 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

Correctness79.5 / 100

The MobilityData validator flagged 5 kinds of issue across 113 instances (0 error, 110 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 363 days.

Rider experience52.5 / 100

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

Accessibility0 / 100

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

2 accessibility depth signals

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (3, 5, 7, 9, 11).

    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.

  • 432 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Kirkwood Ave & Maple St", "Kirkwood Ave & Jackson St IB", "3rd St & Cory Ln", 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 467 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.

  • 1 (red)
  • 11 (brown)
  • 16 (gray)
  • 2S (teal)
  • 2W (teal)
  • 3 (green)
  • 4S (purple)
  • 4W (purple)
  • 5 (red)
  • 6 (brown)
  • 7 (brown)
  • 9 (teal)
Routes in Bloomington Transit's feed
RouteTypeLine color
1 North Fee Lane BHS NorthBusred
11 W 17th / IU Campus ExpressBusbrown
16 West SideBusgray
2S 2 South RogersBusteal
2W 2 West 11th St via Showers ComplexBusteal
3 East College Mall / IU Health HospitalBusgreen
4S 4 South High Street / Sherwood OaksBuspurple
4W 4 West Bloomfield RoadBuspurple
5 Sare RoadBusred
6 Campus ShuttleBusbrown
7 South Walnut / Clear CreekBusbrown
9 IU Campus / College Mall / Covenanter & ClarizzBusteal
List every stop
  • Ivy Tech Inbound
  • Kirkwood Ave & Maple St
  • Kirkwood Ave & Jackson St IB
  • 3rd St & Cory Ln
  • 3rd St & Landmark IB
  • Adams St & Kirkwood Ave
  • Kirkwood Ave & Elm St
  • Rogers & W Prospect
  • Gates Dr & Runkle Way
  • Whitehall Plaza @ Hardee's
  • 3rd & Johnson
  • 3rd St & Kimble Dr
  • 3rd St & Cory Ln
  • 3rd St & Westplex
  • 3rd St & Landmark Ave
  • Kingston Dr & 3rd St
  • Longview & Kingston Dr
  • Rogers St & 1st St
  • Walnut St & 11th St
  • 7th St & Walnut St
  • Washington St & 2nd St
  • Hillside & Henderson
  • Rhorer Rd at the Clear Creek Crossing Shopping Center
  • Pete Ellis Dr & Amy Ln
  • Morningside Dr & Smith Rd
  • 10th St & Barrington Dr
  • Morningside Dr & Sheffield Dr
  • Morningside Dr & Park Ridge Rd
  • Morningside Dr & 3rd St
  • Washington St & Kirkwood Ave
  • Eagleson Ave @ Wells Library
  • 3rd St & Indiana Ave
  • 3rd St @ IU Biology
  • 2nd @ College Mall Apartments
  • 2nd & Woodscrest
  • Kinser Pike at Upper Cascades Skate Park
  • 10th St @ Fountain Park Apartments
  • 10th St & Woodbridge Dr
  • Miller @ Community Health
  • Kingston Dr @ Fifth Third Bank
  • Kingston Dr @ Chick Fil A
  • College Mall East
  • 3rd St and Johnson Ave (eastbound-inbound)
  • 3rd St and Opportunity Lane
  • Liberty Dr @ Whitehall Plaza Kroger
  • 3rd St @ Long John Silver
  • Whitehall Plaza @ Cost Cutters
  • Whitehall Plaza @ Planet Fitness IB
  • Woodside Dr & Park Square Dr
  • Woodside Dr & Sugar Maple Cr
  • Park Square Dr & Sunset Ave
  • College Ave @ CVS
  • 11th & Diamond St
  • Maple & 15th
  • Maple & 13th
  • Maple St & 17th St
  • Maple @ Sunflower Apartments
  • 17th & Jackson
  • Maxwell & Hillside
  • Maxwell & Thornton
  • Winslow & Westminster Way
  • Miller & Maxwell
  • Miller & Covey
  • Miller Drive and Walnut St at Sassafras Hill Apartments
  • Miller @ Walnut Woods
  • Miller & Park Avenue
  • Miller & Henderson
  • Huntington & Miller
  • 10th St & Campbell St
  • 10th St @ Crosstown Plaza
  • Covenanter Dr @ Monroe Apts
  • 3rd & High St
  • 3rd & Clark St at First United Church
  • Clairzz Blvd @ Woods at Latimer
  • Clarizz Blvd and Buick Cadillac Blvd
  • College Ave & 11th St
  • Rogers St & Hillside Dr
  • Rogers St & Patterson St
  • Rogers St & Wilson St
  • Rogers St & Hillside Dr @ Community Kitchen
  • Whitehall Plaza @ Cost Cutters
  • 2nd & Euclid
  • Hickory & Belle
  • Rogers St & Coolidge Dr
  • Covenanter Drive at Toto's Uncle Cafe and the Monroe Apartments
  • Clarizz Blvd @ the Grove at Latimer (Inbound)
  • Clarizz @ The Woods at Latimer (Inbound)
  • 10th St & Union St
  • Atwater Ave & Woodlawn Ave
  • Atwater Ave & Hawthorne Dr
  • 3rd St & Lincoln
  • 3rd St & Grant St
  • Atwater & Fess Ave
  • Atwater Ave & Eagleson Ave
  • 3rd & Eagleson
  • Sare Rd & Olson Dr @ Steeplechase
  • Sare & Southern Oaks
  • Rogers Rd & Sare Rd
  • High & Rock Creek @ Childs
  • High & Greenbriar OB
  • High & Arden
  • Rogers & 3rd
  • Sare & Canada
  • Sare Rd & Creeks Edge Dr
  • Leonard Springs & Fairington
  • Woodland Springs Apartments
  • Leonard Springs & Fairington
  • Leonard Springs & Stapleton
  • Leonard Springs & Maybury Mall
  • Leonard Springs @ Plaza West
  • Leonard Springs & Woodhaven
  • Leonard Springs & Cedar Chase
  • Leonard Springs & Cedar Chase
  • Heatherwood Park
  • College Mall East Shelter
  • Allen @ The Willows
  • Adams & Allen
  • 2nd St @ Health Net
  • 2nd St & Walker St
  • Patterson & 2nd
  • Patterson & Allen
  • 15th St & Lindbergh Dr
  • Illinois & Illinois
  • Fountain Dr & Crescent Rd
  • 17th St & Lismore Dr
  • 12th & Monroe
  • College Mall Rd @ Eastland Plaza
  • Eagleson Ave @ Neal-Marshall
  • Eagleson Ave @ IU MAC
  • College Mall Rd @ College Mall and Eastland Plaza
  • Longview Ave & Pete Ellis
  • Henderson St at Crawford Apartments
  • North Drive and Henderson St
  • North Drive and Walnut St at Bloomington High School South
  • Henderson St and Graham Place
  • Henderson St and South Drive
  • Clarizz Blvd @ Grove at Latimer
  • Walnut St Pk & Allendale
  • Kinser Pike and Parrish Rd
  • Fee @ Foster Quad
  • Dunn & 17th @ Stadium View Apts
  • Fee @ Briscoe Quad
  • 14th & Washington @ The Standard
  • High & Maxwell
  • Maxwell & High
  • Rogers St @ A Friends Place Overnight Shelter
  • Rogers St & Patterson Dr
  • High & Moores Pike
  • High St & Hillside Dr
  • High & Covenanter
  • High & Marilyn
  • Smith Rd & 10th St
  • Smith Rd & McCracken Way
  • Smith Rd & 3rd St
  • Hagan St & Smith Rd
  • Hagan St & Park Ridge Rd
  • Belle & Park Square
  • 10th St & Fee Ln @ Business School
  • Allendale & Dunstan
  • 10th St & SR 45/46 @ UITS
  • Henderson St at Winslow Plaza and Brandon Court
  • Woodlawn Ave and 7th St at Indiana Memorial Union
  • 10th St & Forrest Ave @ Geology and Informatics
  • 7th St and Dunn St
  • 7th St & Grant St
  • Maxwell & Mitchell
  • 3rd St & Patterson Dr
  • Whitehall Plaza & 3rd St IB
  • Hillside & Lincoln
  • Walnut & Grimes
  • Hillside & Walnut
  • Walnut St & Dixie St
  • Walnut & 2nd
  • Walnut and 1st St
  • 3rd & Walnut
  • Walnut St & Smith Ave @ Project School
  • Leonard Springs & Maybury Mall
  • Curry Pike & Glen Oaks
  • Curry Pike & Beasley
  • Curry Pike & Roll Ave
  • Constitution Ave & Liberty Dr
  • Constitution Ave & Curry Pike
  • Liberty Dr @ ALDI
  • Liberty Dr @ Center 37 Professional Facility
  • Curry Pike @ BMV
  • Gifford Rd @ Garden Villa
  • 10th St & Walnut Grove St @ Psychology Building
  • 17th St and Indiana Ave
  • 17th @ Assembly Hall
  • Walnut St and Old State Rd 37
  • Walnut St and 14th St
  • Winding Way & Stonycrest
  • Kinser Pike and Parrish Rd @ the North Kroger Shopping Center (Inbound)
  • Kinser Pike @ BHS North
  • 11th St & Summit St
  • 11th & Orris
  • 11th St & Maple St
  • 11th & Fairview
  • Rogers St & 11th St
  • Rogers St & 10th St at the B Line Trail
  • 7th St & Rogers St
  • Prow Rd @ Meadows Hospital
  • Acuff & Rosewood
  • Kinser Pike & Rosewood
  • Walnut St @ Perry Township Trustee's Office
  • Walnut St & Dixie St
  • Smith Rd & Morningside Dr
  • Sare & Mill Stone
  • High & Arden
  • Leonard Springs & Woodhaven
  • 3rd St & Wynnedale Dr
  • Park Ridge rd & 3rd St
  • Hillside & Dunn
  • Hillside & Palmer
  • 3rd St & Yancy Ln
  • 10th St @ Union St Center
  • College Mall Rd & 2nd St
  • College Mall Rd & Hunter Ridge Apts
  • Sare Rd & Meadow Creek Blvd
  • Rogers Rd & Winding Brook Circle
  • Rogers @ Sherwood Oaks
  • Rogers Rd & Spicewood Ln IB
  • Jackson Creek MS
  • Sare Rd & Canada Dr
  • Sare Rd & Creekds Edge Dr
  • Sare Rd & Olson Dr @ Oaklawn Park
  • Rogers & The Stands OB
  • High St @ Childs ES
  • Curry Pk & Constitution
  • Curry Pike & Heritage Way
  • Woodside & Sugar Maple
  • Woodside Drive @ Orchard Glen
  • Highland Park Elementary
  • Park Square & Sunset
  • Curry Pike & Stebu
  • Gifford & Curry Pk @ Garden Villa OB
  • Woodside Dr & Apple Tree Ct
  • Woodside & Gifford
  • Henderson & Graham
  • Basswood @ Forest Ridge Apts
  • Leonard Springs & SR 45
  • Basswood Dr & Ridge Rd
  • Basswood & Copper Beach Way
  • Basswood & Bloomfield Rd
  • Basswood Apartments
  • Bloomfield & Cory
  • Bloomfield Rd & Rolling Ridge Way
  • Bloomfield Rd & Landmark Ave
  • Leonard Springs @ Wal-Mart Shelter
  • SR 45 @ Wal-Mart
  • and 217 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: 75.32026-07-30: 75.32026-07-31: 76.22026-08-01: 76.2
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2575.3 first check
2026-07-3075.3 no change
2026-07-3176.2 up 0.9
2026-08-0176.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

8 findings, ordered by severity.

Show every finding
  • Warning1000 instances

    1000 of 1000 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 (opens the GTFS Schedule reference on an external site)

  • Warning467 instances

    467 of 467 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 (opens the GTFS Schedule reference on an external site)

  • Warning106 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

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

  • Warning2 instances

    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 (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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

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

  • Info3 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 · 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).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · 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 363 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 1000 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 0% of trips; the mark needs 90% of each.

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

  • 2 of 467 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 363 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 80 / 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 52 / 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.

Bloomington Transit GTFS data quality grade: C

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/bloomington-transit-2066/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.