← All agencies

Feed status · checked 2026-08-02

Rabbit Transit

Based on the feed this agency publishes

Service mode Bus

FDCBA

34.6 / 100

up 0.1 since 2026-08-01 · F → F

Catalogued in Pennsylvania.

Feed expiredAccessibility 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 37 minutes 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

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool

Service data ended 1310 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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

674 of 674 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 03

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

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

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: Service data ended 1310 day(s) ago.
Next action: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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: Rabbit Transit
Finding: scorecard_feed_expired
Feed evidence: Service data ended 1310 day(s) ago.
Why it matters: When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Requested change: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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.
Evidence: https://gtfsscorecard.org/agency/rabbit-transit/?finding=scorecard_feed_expired#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.

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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.
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.
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.

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 was 1310 days ago.
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.

Hi,

Our GTFS feed (Rabbit Transit) scored F (34.6 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
   What: Service data ended 1310 day(s) ago.
   Finding code: scorecard_feed_expired
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expired/

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 674 of 674 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 2878 of 2878 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/rabbit-transit/

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Hi Rabbit Transit team,

Service data ended 1310 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/rabbit-transit/

Score by category

Correctness41.5 / 100

The MobilityData validator flagged 11 kinds of issue across 17967 instances (0 error, 17962 warning, 5 informational).

Freshness0.0 / 100

Service data ended 1310 day(s) ago. Trip planners have likely already dropped this feed.

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.

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

1W (red)
10S (green)
1E (black)
12 (red)
13 (green)
16 (pink)
2N (orange)
20N (green)
20S (brown)
22N (orange)
3N (green)
32 (black)
33 (blue)
4E (brown)
5W (orange)
5E (red)
6N (teal)
LL2 (red)
LL1 (red)
BL (blue)
GL (gray)
15N (green)
GHC (brown)
8S (brown)
83N (black)
83S (gray)
9S (teal)

Routes in Rabbit Transit's feed
Route	Type	Line color
1W West Manchester Town Center	Bus	red
10S South York Plaza / Red Lion	Bus	green
1E East York	Bus	black
12 Wrightsville / Columbia	Bus	red
13 Dover / UPMC Hospital	Bus	green
16 York to Hanover	Bus	pink
2N North York Via N George St	Bus	orange
20N North Hanover via Kindig	Bus	green
20S South Hanover via Baltimore	Bus	brown
22N North Hanover via Randolph	Bus	orange
3N Northwest Plaza / UPMC Hospital	Bus	green
32 Apple Hill Shuttle	Bus	black
33 Industrial Park Shuttle	Bus	blue
4E East York via Princess	Bus	brown
5W West York / West York Ind Park	Bus	orange
5E Haines Rd / Greensprings	Bus	red
6N HACC / Manchester Ind Park	Bus	teal
LL2 Lincoln Line 2 (Outlets)	Bus	red
LL1 Lincoln Line 1 (Aspire Hotel)	Bus	red
BL Blue Line	Bus	blue
GL Gray Line	Bus	gray
15N Gettysburg Express	Bus	green
GHC GB - HAN Connector	Bus	brown
8S York Hospital via George	Bus	brown
83N Harrisburg Express	Bus	black
83S Northern Maryland Express	Bus	gray
9S York Hospital via Pershing	Bus	teal

List every stop

Galleria Mall - Boscovs
S. 2nd St. at Vine St.
South York Park and Ride
US Rt 30 at S Salem Church Rd
Apple Hill Medical Center
Wilson Ave at York St
South Hanover Shopping Center
E. Princess St. at Pine St. ib.
Borom Rd. at Clugston Rd.
Broadway at Ridge Ave.
W Philadelphia St at Sumner St
Fairmount Rd. at Dulaney Valley Rd.
S. Pershing Ave. at College Ave. ob.
George St. at Sunset Ln.
York Town Center
2nd St at Market St
W King St at Richland Ave ib.
Harrisburg - PHEAA Building
Harrisburg - HACC Campus
Hunt Valley Light Rail
McCormick Rd. at Shawan Rd. nb
McCormick Rd. at Schilling Rd. sb
McCormick Rd. at Wight Ave. sb
McCormick Rd. at Wight Ave. nb
11100 McCormick Rd. sb
11019 McCormick Rd nb
Beaver Dam Rd. at Swim Club sb
Beaver Dam Rd. at Swim Club nb
Beaver Dam Rd. at Cockeysville Rd.
Market St. at Broad St. ib.
10610 Beaver Dam Rd. sb
Beaver Dam Rd. at Beaver Ct. nb
Industry Ln. at Beaver Dam Rd.
Timonium Light Rail
10909 McCormick Rd. nb
Shrewsbury Park and Ride
Commerce Square Shopping Center ib.
Expedition Trail ib.
DGS N. Circle Drive
DGS Dogwood Dr.
DGS Dogwood Dr. at Sycamore St.
Espresso Way at Ollie's
York County Prison ib.
Carlisle Rd. at Pine Rd. ob.
Carlisle Ave. at Poplars Rd. ob.
Palomino Rd. at YMCA ob.
Carlisle Rd. at Fox Run Rd. ib.
Church St. at Carlisle Rd. ob.
Hunt Ave Parking NB
Carlisle Rd. at Stony. Ln.
Williams Road
Eisenhower Complex
Bannister St. at Seward Ave. ob.
Gettysburg Battlefield Resort
W. Market St. at Clinton St. ib.
Madison St. at Kindig Ln.
YWCA Gettysburg & Adams County
W. Market St. at Diamond St. ob.
Steinwehr Ave.at King St. ob..
West York Industrial Park
Spahn Ave. at Ogontz St.
Greensprings Plaza
Haines Rd. - Salvation Army
Dawn Foods
Dewey St. at King St. ob.
Bannister St. at Clinton St. ib.
Rt. 462 at Broad St.
W. Jackson St. at Cleveland Ave. ib.
Jefferson Ave. at Pershing Ave. ob.
George St. at Jefferson St. ob.
N. George St. at Fifth St. ib.
Edgar St. at Irving Rd. ob.
York Hospital - Main Entrance
Thomasville Post Office ib.
Broad Park ob.
Old Memorial - Outpatient
E. Main St. at Pleasant Ave. ob.
AHMC Entrance F
Yocumtown Park and Ride
Northwest Plaza
Maryland Ave. at Roosevelt Ave. ob.
S. George St. at Jackson St. ob.
N. Beaver St. at Lincoln Dr. ib.
Cinema Dr. at Market St.
Edgar St. at Irving Rd. ib.
OSS Health - Powder Mill
E. Market St at Harrison St ob.
East York Walmart
Dillsburg Park and Ride
Pleasant Acres Home
S. Broad St. at E. King St ib.
E. Philadelphia St. at Harrison St.
W. Philadelphia St.at Carlisle Ave.
ES3 Prison Stop
W. Market St. at Belvidere Ave. ib.
ES3
Neu Rd. at Pennsylvania Ave.
York Rd. at W Pennsylvania Ave.
111 Chesapeake Ave.
Hanover Hospital
N. Hanover Mall
Hanover Crossing Shopping Center
Hanover - Gateway
Davies Rd. at Heindel Rd. ob.
N. George St. at Gas Aly. ib.
Brougher Ln. at Haviland Rd. ib.
York Crossing Dr. at Carlisle Rd.
308 St. Charles Way Nefrology ob.
White St. ib. at York Scout Shop
Bannister St. at Seward St. ib.
Carlisle Ave. at Florida Ave. ib.
Carlisle Ave. at Madison Ave. ib.
Carlisle Ave. at Philadelphia St.
W. Market St. at Hartley St. ib.
W. Market St. at West St. ib.
W. Market St. at Newberry St. ib.
HACC Campus YCIP
W King St. at Beaver St. ob.
N. Beaver St. at Market St. ob.
W. Philadelphia St. at Beaver St.
W. Philadelphia St. at Newberry St.
Philadelphia St. at Roosevelt Ave.
W. Philadelphia St. at Hartley St.
W. Philadelphia St. at West St.
Philadelphia St. at Belvidere Ave.
Carlisle Ave. at Linden Ave. ob.
Carlisle Ave. at Madison Ave. ob.
Carlisle Ave. at Florida Ave. ob.
Carlisle Ave. at Texas Ave. ob.
Bannister St. at Clinton St. ob.
White St. at Bannister St. ob.
Commerce Square Shopping Center ob.
Brougher Ln. at Haviland Rd. ob.
Loucks Rd. ob. At Tires Plus
Loucks Rd. at Kenneth Rd. ob.
Rodney Rd. at Kenneth Rd. ob.
E. Market St. at Queen St. ob.
E. Market St. at Broad St. ob.
E. Market St. at State St. ob.
E. Market St. at Sherman St. ob.
E. Market St. at Tremont St. ob.
Hellam St. at 3rd St. ob.
E. Market St. at Albemarle St. ob.
E. Market St. at Lehman St. ob.
E. Market St. at Ogontz St. ob.
E. Market St. at Yale St. ob.
E. Market St. at Eastern Blvd. ob.
E. Market St. at Keesey St. ob.
E. Market St. at Vernon St. ob.
E. Market St. at Kershaw St. ob.
E. Market St. at Royal St. ob.
2500 E. Market St. ob.
Industrial Hwy. at Memory Ln. ob.
300 Memory Ln. ob.
Pleasant Valley Rd.at Whiteford Rd.
Galleria West - Target
2902 Pleasant Valley Rd. ob.
2900 Whiteford Rd. ob.
E. Market St. at Lyndhurst Rd. ib.
UPMC Hospital
2901 E. Market St. ib.
E. Market St. at York Marketplace
E. Market St. at Royal St. ib.
E. Market St. at Kershaw St. ib.
E. Market St. at Vernon St. ib.
E. Market St. at Keesey St. ib.
E. Market St. at Marshall St. ib.
E. Market St. at Oxford St. ib.
E. Market St. at Yale St. ib.
E. Market St. at Ogontz St. ib.
E. Market St. at Harrison St. ib.
E. Philadelphia St. at Eberts Ln.
E. Philadelphia St.at Albemarle St.
E. Philadelphia St. at Tremont St.
E. Philadelphia St. at Sherman St.
York COVID-19 Vaccination Site
E. Philadelphia St. at Franklin St.
E. Philadelphia St. at State St. ib.
E. Market St. at Mills St. ib.
E. Philadelphia St. at Pine St. ib.
E. Philadelphia St. at Queen St. ib.
E. Philadelphia St. at Duke St. ib.
3300 Concord Rd. ob.
York County Prison ob.
Concord Rd. at Heindel Rd. ob.
3550 Concord Rd. ob.
Delco Center
Davies Rd. at Concord Rd. ob.
E. Philadelphia St at Broad St ib.
Duke St. at College Ave. ib.
Pleasant Acres Stony Brook Manor ib.
3641 E. Market St. ib.
3603 E. Market St. ib.
Main St. at Railroad St. ib.
3441 E. Market St. ib.
E. Market St. at Bloomingdale Ave.
Joppa Rd. just past Black Decker
E. King St. at Court St. ob.
Duke St. at Philadelphia St. ob.
213 N. Duke St. ob.
North St. at Court St. ob.
N. George St. at Revolution Stadium
N. George St. at 6th Ave. ob.
N. George St. at Parkway Blvd. ob.
E. Walnut St. at York St.
N. George St. at E. 4th Ave. ob.
N. George St. at 5th Ave. ob.
N. George St. at 8th Ave. ob.
N. George St. at 10th Ave. ob.
W. 11th Ave. at N. George St. ob.
W. 11th Ave. at Northgate SC ob.
Pennsylvania Ave. at Fireside Rd.
Pennsylvania Ave. at Kelly Dr. ib.
Pennsylvania Ave. at June St. ib.
Pennsylvania Ave at Priority Rd. ib.
Parkway Blvd. at N. Newberry St. ib.
N. Pershing Ave. at Parkway Blvd.
N. Pershing Ave. at Front St. ib.
Jefferson St. at N. Pershing Ave.
E. King St. at S. Queen St. ob.
S. Pine St. at Princess St. ob.
W. Cottage Pl. at S. Newberry St.
W. Jackson St. at Newberry St. ob.
W. Jackson St. at Pershing Ave. ob.
E. Cottage Pl. at Edgar St. ob.
Edgar St. at Jackson St. ob.
Edgar St. at Rockdale Ave. ob.
Rathton Rd. at S. Pine St. ob.
Board Rd at Church Rd ib.
Locust St. at 3rd St.
Shrewsbury Food Lion
OSS Health - Roosevelt Ave
S. George St. at Colonial SC ib.
S. George St. at Sprinettsbury Ave.
S. Pershing Ave. at Cottage Pl. ib.
S. Pershing Ave. at Lafayette St.
S. Pershing Ave. at E. College Ave.
Candlewood Suites - York
Roosevelt Ave. at Gas Ave. ob.
Roosevelt Ave. at Lincoln St. ob.
Roosevelt Ave. at Linden Ave. ob.
Roosevelt Ave. at Rockdale Aly. ob.
Roosevelt Ave. at Tioga St. ob.
Roosevelt Ave. at Wood St. ob.
Roosevelt Ave. at Chanceford St. ob.
Roosevelt Ave. at Fahs St. ob.
Roosevelt Ave. at Belaire Ln. ob.
Roosevelt Ave. at Marbrook Ln. ob.
Roosevelt Ave. at Marbrook Ln. ib.
1230 Roosevelt Ave. ib.
and 424 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — up 0.1 since 2026-08-01.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	34.5	first check
2026-07-30	34.5	no change
2026-08-01	34.5	no change
2026-08-02	34.6	up 0.1

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

What changed in this feed

Overall score rose 0.1 points since 2026-08-01.

Same feed file as 2026-08-01; 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

15 findings, ordered by severity.

Show every finding

Error1 instance
Service data ended 1310 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning7899 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)
Warning6830 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 (opens the validator rules on an external site)
Warning2878 instances
2878 of 2878 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)
Warning2845 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning674 instances
674 of 674 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)
Warning368 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning5 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning3 instances
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)
Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · 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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info5 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 (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 Not ready

Resolve this before you certify on the D-10. Service data expired 1310 days ago, so FTA would find the link out of date.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Not ready: Service data expired 1310 days ago, so FTA would find the link out of date.
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 2878 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. Service data expired 1310 days ago. 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 Not yet: Service data expired 1310 days ago.
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.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

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 42 / 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 0 / 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.

[![Rabbit Transit GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/rabbit-transit/badge.svg)](https://gtfsscorecard.org/agency/rabbit-transit/)

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/rabbit-transit/2026-08-02.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-02. 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). Rabbit Transit GTFS feed-quality record, dated 2026-08-02 (grade F (34.6/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 0efc0489e050…). https://gtfsscorecard.org/data/artifacts/rabbit-transit/2026-08-02.json

@misc{gtfsscorecard-rabbit-transit-2026-08-02,
  title        = {Rabbit Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/rabbit-transit/2026-08-02.json}},
  note         = {Checked 2026-08-02; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade F (34.6/100)}
}

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