Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires

Feed status · checked 2026-07-09

Red Rose Transit Authority (RRTA)

Based on the feed this agency publishes

FDCBA

71.3 / 100

unchanged since 2026-07-08

Ahead of 62% of all tracked agencies and 79% of large agencies. Operates in Pennsylvania.

Covers 540 daysAccessibility gapsNo realtime feed

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

Checked for changes 6 hours ago; last changed 8 days ago.

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

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

Fix 02

Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool

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

⏱ Often one default setting in your export.worth about +15 points

Agencies here usually clear this within about 1 week (based on 5 observed fixes).

Fix 03

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.

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

Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.

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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.

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 (Red Rose Transit Authority (RRTA)) scored C (71.3 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

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

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
   What: 3286 of 3286 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. 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.
   What: The feed contains no fare information.
   Validator notice: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/red-rose-transit-authority-rrta-2000/

Score by category

Correctness79.0 / 100

The MobilityData validator flagged 6 kinds of issue across 95 instances (0 error, 93 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 540 days.

Rider experience37.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 not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, 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.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

1 (red)
10 (blue)
11 (teal)
12 (teal)
13 (yellow)
14 (orange)
15 (green)
16 (black)
17 (brown)
18 (brown)
19 (pink)
20 (purple)
21 (green)
3 (purple)
5 (purple)
6 (purple)
8 (purple)
MU X (green)

Routes in Red Rose Transit Authority (RRTA)'s feed
Route	Type	Line color
1 Northeast McCaskey	Bus	red
10 Lititz	Bus	blue
11 Ephrata	Bus	teal
12 New Holland	Bus	teal
13 White Horse	Bus	yellow
14 Rockvale Outlets	Bus	orange
15 Willow Street	Bus	green
16 Millersville	Bus	black
17 Columbia	Bus	brown
18 Elizabethtown	Bus	brown
19 Manheim	Bus	pink
20 Greenfield	Bus	purple
21 Gap	Bus	green
3 Sterling Place	Bus	purple
5 Golden Triangle	Bus	purple
6 Hawthorne Centre	Bus	purple
8 Park City	Bus	purple
MU X MU Xpress	Bus	green

This feed has 1271 stops.

List every stop

W. Chestnut & N. Queen
Rt. 462 & Maleable Rd.
14th St. & Rt. 462
Manor & 14th St.
Manor & 12th St.
Manor & 10th St.
manor & Plane St.
Manor & 4th St.
4th & Mill St. at shelter
4th & Union St. at shelter
4th & Cherry St.
Courthouse Duke & Grant
Locust St. & Rt. 462 Lancaster Ave.
Locust & 6th St. at CVS
Locust & 8th St.
Locust & 9th St.
9th & Walnut St.
Cnestnut & 9th St.
Chestnut & 7th St.
Chestnut & 5th St. Rt. 462
Chestnut & 3rd St.
3rd. & Poplar St.
Maple & 3rd St.
Linden & 3rd St.
3rd St. & Rt. 30 at Burger King
Rt. 441 & Breezywood Dr.
Rt. 441 & Klinesville Rd.
Rt. 441 & Hazel Ave.
Market St. & Rt. 441
Market & N. Bank St.
Market & Division St.
Market & Pine St.
Rt 23 and Eden Rd.
Market & Chestnut St.
Market & New Haven St.
Market & Mulberry St.
Market & Gay St. Market Sq.
Market & Bridge St.
Market & Jones St.
Dacatur & Market St.
Decatur & Wasp St.
Decatur St. & Rt. 441
Rt. 441 & Waterford Ave.
Rt. 441 & Bank St.
Rt. 441 & Market St. Rt. 23
Rt. 441 & River Rd.
Rt. 441 & Cardinal Dr.
3rd. & Chestnut St.
3rd & Walnut St.
Locust & 3rd St. shelter
Manor & Florence St.
Manor & 9th St.
18th St. at Weis Market
Rt. 462 & 15th St.
Rt. 462 & Laurel Run
Rt. 462 across from Hot Z Pizza
Rt. 462 at Kmart & St. Anne's shelter
Rt. 462 & Maria Lane
Rt. 462 at Mountville Pool
Rt. 462 & Village Dr.
Rt. 462 & Hershey Mill Rd.
Donnerville Rd. across from Shea Roofing
S. Marshall & King
Donnerville Rd. at Core State
Hempland & Donnerville Rd.
Hempland Rd. at Huttig
Hempland Rd. at Hubbard Grain
Hempland Rd. at Purina
Hempland Rd. at Unclaimed Freight
Hempland & Centerville Rd.
Rt. 462 at Morgan Towing
East End & S. Marshall
Rt. 462 at Leisure Lanes
Rt. 462 & Weaver Rd.
Rt. 462 & Centerville Rd.
Rt. 462 at Manor West Commons
Rt. 462 across Villa Nova Restaurant
Rt. 462 at Super Shoes
Rt. 462 at Colonial News
Rt. 462 at Armstrong Industries
Rt. 462 & Millersville Rd.
Rt. 462 & Hawthrone Dr.
East End & S. Ann
Rt. 462 & Eastman Ave.
Rt. 462 & Dickenson Ave.
Rt. 462 & Bucknell Ave.
Rt. 462 & Cornell Ave.
Columbia Avenue & Stone Mill Rd.
Rt. 462 & Stone Mill Plaza
Rt. 462 at Taco Bell
Rt. 462 & School Lane
Rt. 462 & President Ave.
Rt. 462 & Rider Ave.
S. Ann & Green
Rt. 462 & West End Ave.
Columbia Ave. & Pearl St.
W. King & Ruby St.
W. King & Coral St.
W. King & Dorwart St.
W. King & Mary St.
W. King & Strawberry St.
W. King & Mulberry Water St. (mid-block)
N. Queen & King Fulton Bank
W. Walnut & N. Queen St.
New Dauphin & S. Ann
W. Walnut & N. Prince St.
W. Walnut & Mulberry St.
W. Walnut & N. Mary St.
W. Walnut & Nevin St.
Collage Ave. & Walnut St.
Marietta & West End Ave.
Marietta & Race Ave.
Marietta & N. President Ave.
Marietta Ave. & N. School Lane
Marietta Ave. & Hamilton Rd.
Marietta & Wilson Ave.
1433 Marietta Pk.
Marietta Pk. & River Dr.
Marrietta Pk. & Oakwood lane
Marietta Pk. & Hedgwick Dr.
Marietta Ave. & Barr Blvd.
Marietta Pk. & Farmingdale Rd.
Marietta Pk. & Good Dr.
2011 Marietta Pk.
2115 Marietta Pk.
New Dauphin & S. Reservior
Marietta Pk. & Rohrerstown Rd.
Marietta Pk. & Elizabeth St.
2435 Marietta Pk.
Marietta Ave. & Pin Oak Dr.
Marietta Ave. & Running Pump Rd.
Marietta Ave. & Beech Ln.
Marietta Ave. & Dorsea Rd.
Marietta Ave. & Peacock Dr.
Marietta Ave. & Imperial Dr.
Marietta Ave & Robin Rd.
S. Broad & Clermont
Marietta Ave. & Centerville Rd.
3019 Marietta Ave.
3045 Marietta Ave. Oyster Pt. Medical
Stony Battery Rd. & Hathaway St.
Stony Battery Rd. & Pine Tree Way
Stony Battery Rd. & Church St.
Stony Battery Rd. & Ivy Dr.
Stony Battery Rd. at QVC
Stony Battery & Nolt Rd.
S. Broad & Circle Ave.
Stony Battery & Kauffman Rd.
Kauffman Rd. & Church St.
Church St. & Camp Meeting Rd.
Main & Church
Main & C St.
Main St. & Lanco Sq.
Main & Cooper St.
Main & James St.
Main & G St.
Main St. & Stony Battery Rd.
Chesapeake & S. Franklin
Main St. & Holland Ave.
Rt. 20 & Esbenshade Rd. at Sheetz
1387 Rt. 230 at Eby Chiques Rd.
E. Main & Necomer St.
E. Main & Lefever
E. Main St. & Joy Ave.
E. Main & Jacob St.
E. Main & Barbara St.
S. Ann & Chesapeake
E. Main & Market St.
W. Main & Manheim St.
W. Main at American Legion
W. Main & Orchard Rd.
W. Main & Orange St.
W. Main & Angle St.
W. Main & Plum St.
955 W. Main St.
Market St. & Cloverleaf Rd.
S. Ann & Susquehanna
Market St. & Larkspur Lane
Market St. & Shaeffer Rd.
1255 S. Market St.
Market St. & Groff Ave.
Market & Spruce St.
Market St. & College Ave.
Market & Washington St.
Market & Park St.
S. Ann & Juniatta
Masonic Dr. & Shrine Rd.
Bainbridge St. & Masonic Dr.
Bainbridge St. at Mars Dove factory
Bainbridge & Market St.
Market & Arch St.
Market St. & Maytown Rd.
Market St. at Giant
Market St. & Shaeffer Rd.
Market St. & Snyder Rd.
S. Lime & Juniatta
964 Main St.
334 Main across from Turkey Hill
230 W. Main St.
Main & New Haven St.
330 E Main St. at shelter
Main & Longenecker
740 E Main St.
890 E. Main St.
960 E. Main St.
Main St. & Cornerstone Dr. at shelter
Dauthin & S. Lime
Rt. 230 & Eby Chiques Rd.
E. Main & Esbenshade Rd. across Sheetz
Main St. & Stony Battery Rd.
Main St. & Cooper Ave.
Main & Broad St.
Main & Elizabeth St.
Church & Main St.
Church & Bank St.
Kauffman Rd. & Church St.
Kauffman & Stony Battery Rd.
Dauphin & S. Duke
Stony Battery Rd. at QVC shelter
Stony Battery & Indian Springs Rd.
Stony Battery Rd & Kayo Ave Turkey Hill
Marietta Ave. & Stony Battery Rd.
Marietta Ave. & Imperial Dr.
2544 Marietta Ave.
Marietta Ave. & Elizabeth St.
Marietta Ave & Rohrerstown Rd.
Marietta Ave. & Northlawn Dr.
S. Duke & North
Marietta Ave. & N. President Ave.
Marietta & College Ave.
W. Chestnut & Nevin St.
W. Chestnut & Mary St.
W. Chestnut & Charlotte St.
W. Chestnut & Water St.
HACC campus at Shelters
107 Pitney Rd. at Flexsteel
S. Duke & Howard
Pitney Rd. & Morris Parkway
Pitney Rd. & Princess Anne Dr.
207 Pitney Rd.
Pitney & hempstead Rd.
Hempstead Rd. at Lowes Best Buy Dr.
E. Farnum & Church
E. Farnum & S. Queen
Wm. Penn Way & Greenfield Rd.
1824 Hempstead Rd. at Costco
Pitney & Glenn Rd.
Pitney Rd. & Princess Anne Dr.
Pitney Rd. & A. E. Morris Pkwy.
106 Pitney Rd. Non HACC trips
and 1021 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-06-19	73.2	first check
2026-06-20	73.2	no change
2026-06-21	73.2	no change
2026-06-22	73.2	no change
2026-06-23	73.2	no change
2026-06-24	73.2	no change
2026-06-25	73.5	up 0.3
2026-06-26	73.5	no change
2026-06-27	73.5	no change
2026-06-28	73.5	no change
2026-06-29	73.5	no change
2026-06-30	71.3	down 2.2
2026-07-01	71.3	no change
2026-07-02	71.3	no change
2026-07-04	71.3	no change
2026-07-05	71.3	no change
2026-07-06	71.3	no change
2026-07-07	71.3	no change
2026-07-08	71.3	no change
2026-07-09	71.3	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-08.

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

Warning3286 instances
3286 of 3286 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning1271 instances
1271 of 1271 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning89 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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)
Warning2 instances
Some route colors don't contrast with their text color.
Route badges become unreadable, especially for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 7 observed fixes).
Validator rule: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: future_feed · 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 10, 11, 12, 13, and more).
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.
1030 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("W. Chestnut & N. Queen", "Rt. 462 & Maleable Rd.", "14th St. & Rt. 462", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

NTD certification readiness Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 540 days.

agency_id matches your NTD ID Not checked yet: Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.

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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 540 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 540 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

A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.

Correctness 79 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
Freshness 100 / 100: The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
Rider experience 38 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily and links back to this scorecard.

[![Red Rose Transit Authority (RRTA) GTFS data quality grade: C](https://gtfsscorecard.org/data/artifacts/red-rose-transit-authority-rrta-2000/badge.svg)](https://gtfsscorecard.org/agency/red-rose-transit-authority-rrta-2000/)

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/red-rose-transit-authority-rrta-2000/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Red Rose Transit Authority (RRTA) GTFS feed-quality record, dated 2026-07-09 (grade C (71.3/100), rubric v1.1, gtfs-validator 8.0.1, feed sha256 7861016a436c…). https://gtfsscorecard.org/data/artifacts/red-rose-transit-authority-rrta-2000/2026-07-09.json

@misc{gtfsscorecard-red-rose-transit-authority-rrta-2000-2026-07-09,
  title        = {Red Rose Transit Authority (RRTA) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/red-rose-transit-authority-rrta-2000/2026-07-09.json}},
  note         = {Checked 2026-07-09; rubric v1.1; gtfs-validator 8.0.1; grade C (71.3/100)}
}

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