← All agencies

Feed status · checked 2026-10-20

County of Lackawanna Transit System (COLTS)

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

Service mode Bus

FDCBA

63.6 / 100

First scorecard for this agency

Cataloged in Pennsylvania.

Covers 72 daysAccessibility gapsRealtime not yet published

Source feed: https://coltsivl.availtec.com/InfoPoint/gtfs-zip.ashx

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

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: medium.

Realtime quality was not measured this run. It does not count against the grade.
The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

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

About this feed

County of Lackawanna Transit System (COLTS)’s published feed lists 24 bus routes, 681 scheduled trips and 1,424 stops. Its service dates run from 2026-09-15 through 2026-12-31.

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

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

Fixing this covers all 1,424 stops in the feed.

⏱ 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

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

Fixing this covers all 681 trips in the feed.

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

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A few minutes per flagged trip.worth about +8 points in its category

Riders and need behind these fixes

No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
Pennsylvania as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-19.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: County of Lackawanna Transit System (COLTS)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 1424 of 1424 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/?finding=scorecard_wheelchair_boarding_unknown#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.

Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Fix 03 · Read the fix guide for fast_travel_between_consecutive_stops
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 72 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.

Hi,

Our GTFS feed (County of Lackawanna Transit System (COLTS)) scored D (63.6 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: 1424 of 1424 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/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 681 of 681 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/

3. Check the flagged stop times for transposed minutes.
   What: Some scheduled trips move faster between stops than a bus can.
   Finding code: fast_travel_between_consecutive_stops
   Guide: https://gtfsscorecard.org/fix/fast_travel_between_consecutive_stops/

Full scorecard: https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/

Score by category

Correctness61.2 / 100

The MobilityData validator flagged 7 kinds of issue across 7240 instances (0 error, 7194 warning, 46 informational).

Freshness100.0 / 100

Service data covers the next 72 days.

Rider experience37.6 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is 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 1424 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.

11 (green)
12 (green)
13 (green)
18 (red)
21 (red)
25 (green)
26 (red)
28 (blue)
31 (green)
32 (red)
34 (blue)
35 (purple)
36 (blue)
40 (black)
41 (red)
44 (red)
52 (blue)
54 (orange)
55 (green)
71 (brown)
72 (brown)
73 (teal)
80 (orange)

Routes in County of Lackawanna Transit System (COLTS)'s feed
Route	Type	Line color
11 MID-VALLEY INDUSTRIAL	Bus	green
12 JESSUP	Bus	green
13 DRINKER-MARYWOOD	Bus	green
18 PETERSBURG	Bus	red
21 LAKE SCRANTON	Bus	red
25 VALLEY VIEW / HILLTOP	Bus	green
26 MOHEGAN SUN / WB VA	Bus	red
28 PITTSTON	Bus	blue
31 OLD FORGE	Bus	green
32 TAYLOR EXPRESS	Bus	red
34 KEYSER LAFAYETTE SATURDAY	Bus	blue
35 KEYSER VALLEY	Bus	purple
36 LAFAYETTE	Bus	blue
40 LUZERNE / PROVIDENCE	Bus	black
41 HIGH WORKS	Bus	red
44 CLARKS SUMMIT	Bus	red
52 CARBONDALE	Bus	blue
54 DICKSON CITY VIA MAIN AVE	Bus	orange
55 SHOPPERS SPECIAL	Bus	green
71 CITY CIRCLE NORTH	Bus	brown
72 CITY CIRCLE SOUTH	Bus	brown
73 SATURDAY NORTH / SOUTH	Bus	teal
80 COMMERCE LOOP	Bus	orange
9 CROWD MOVER	Bus	blue (no shape in feed)

List every stop

110 WYOMING AVE
TRANSIT CENTER
LACKA N 7TH O
LACKA / N 9TH
LACKA CABRINI O
NMAIN LACKA O
LAFAY NMAIN O
LAFAY NHYDE O
LAFAY NBROMLY O
LAFAY NSUMNER O
LAFAY NLINCLN O
LAFAY NREBCCA O
LAFAY NGARFLD O
LAFAY NFILMORE
LAFAY NEVERT O
LAFAY NVBURN O
NVBURN PRICE O
NVBURN JACKS O
SVBURN WASHBRN
WASHBN GRANT O
WASHBN SSHERMN
SDEWEY WASHBN O
SDEWEY JACKS O
JACKS MERRIFD O
JACKS NCAMRN O
JACKS KEYSER O
KEYSER BRIGGS O
COLTS I
KEYSER/BRIGGS I
KEYSER LAFAY I
KEYSER PRICE I
KEYSER/JACKS I
JACKS SCAMRN I
JACKS SMERRIFD
JACKS SDEWEY I
SDEWEY WASHBN I
WASHBN SSHERMN
WASHBN SVBURN I
SVBURN JACKS I
NVBURN PRICE I
NVBURN LAFAY I
LAFAY NEVERT I
LAFAY FILMRE I
LAFAY NGARFLD I
LAFAY NREBCCA I
LAFAY NLINCLN I
LAFAY NSUMNER I
LAFAY NBROMLY I
LAFAY NHYDE I
LAFAY NMAIN I
NMAIN LACKA I
LACKA CABRINI I
LACKA N9TH I
LACKA N7TH I
JACKSN CABRINI
S MAIN/JACKSN O
S MAIN WASHBN O
S MAIN DIVISN O
S MAIN LUZRN O
S MAIN HAMPTN O
S MAIN EYN O
S MAIN W ELM O
S MAIN W LOC O
S MAIN DARMTH O
S MAIN BRYNM O
S MAIN AMHRST O
S MAIN WATSN O
S MAIN RUNDL O
S MAIN REYNLDS
WALMART TAYLOR
PRICE CHOPPER
NMAIN RKLDG O
NMAIN OAK TAY O
400 N MAIN O
N MAIN RR CT O
N MAIN CHRCH O
S MAIN W GRV O
S MAIN W TAYLR
S MAIN W ATHER
S MAIN DAVIS O
S MAIN HANCK O
800 S MAIN TAY
S MAIN HOSP O
S MAIN CENTER O
S MAIN SIBLY O
N MAIN MCCLR O
N MAIN DUNN O
N MAIN POWELL O
N MAIN VINE O
OLD FORGE MUN O
S MAIN GRACE O
S MAIN W MARY O
S MAIN HENDRSN
S MAIN DRAKES O
S MAIN HARRSN O
S MAIN W MORTN
S MAIN FALN CT
S MAIN HENDRSN
S MAIN E MARY I
S MAIN GRACE I
OLD FORGE MUN I
S MAIN OAK OF I
N MAIN VINE I
N MAIN POWELL I
N MAIN E DUNN I
N MAIN E MCCLR
S MAIN E SIBLY
S MAIN CENTER I
S MAIN HOSP I
801 S MAIN TAY
733 S MAIN TAY
S MAIN HANCK I
S MAIN DAVIS I
S MAIN E ATHER
S MAIN E TAYLR
S MAIN E GRV I
S MAIN & DAVIS STREET
N MAIN CHRCH I
N MAIN RR CT I
N MAIN OAK TAY
NMAIN RKLDG I
S MAIN RUNDL I
S MAIN WATSN I
S MAIN SMITH I
S MAIN ARCH I
S MAIN W LOC I
S MAIN W ELM I
MAIN/REGAN I
S MAIN FLWS PK
S MAIN DIVISN I
S MAIN WASHBN I
S MAIN/JACKSN I
JACKSN CABRINI
N 9TH LACKA I
N MAIN SWETLND
N MAIN HWLL O
N MAIN PETTI O
N MAIN SCHLAGR
N MAIN ORAM O
N MAIN/W GIBSON
N MAIN SCHLAGR
N MAIN PETTI I
N MAIN HWLL I
N MAIN SWETLND
N SOUTH LOOP O
NSOUTH KEYSER O
KEYSER FERDND O
KEYSER STANTN O
KEYSER OAK SC
KEYSEROAK OLLIE
KOAK DOLLR STR
KEYSER STANTN I
KEYSER FERDND I
NSOUTH LOOP I
HG VMNT MALL O
VIEWMONT MALL
SUMIT PT I
WYOMNG LINDEN I
LACKA S / WASH
100 BLK S WASH
S WASH HICKRY O
WASHINGTN/MAPLE
S WASH E ELM O
E ELM 3RD
4TH BELLVU O
4TH FELLOWS O
RAILRD LUZERNE
LUZERNE MERIDN
LUZERNE 8TH O
LUZERNE 9TH O
LUZERNE 10TH O
LUZRN S MAIN O
LUZRN S HYD PK
LUZERNE 12TH O
LUZERNE 13TH O
LUZERNE 14TH O
LUZERNE 15TH O
LUZERNE 16TH O
LUZERNE 17TH O
LUZERNE 18TH O
LUZERNE 19TH O
LUZERNE 20TH O
LUZERNE 21ST O
LUZRN S SHERMN
200 BLK SSHRMN
SSHERMN WASHBN
200 BLK SSHRMN
S SHRMN LUZRN I
LUZERNE 21ST I
LUZERNE 20TH I
LUZERNE 19TH I
LUZERNE 18TH I
LUZERNE 17TH I
LUZERNE 16TH I
LUZERNE 15TH I
LUZERNE 14TH I
LUZERNE 12TH I
LUZRN S HYD PK
LUZRN S MAIN I
LUZERNE 10TH I
LUZERNE 9TH I
LUZERNE 8TH I
LUZERNE MERIDN
LUZERNE RAILRD
S WASH E ELM I
S WASH MAPLE I
S WASH HICKRY I
ADAMS LACKA I
N 9TH / LACKA
OAK STAUFR IND
STAUF KANE LN
STAUFR AT UPS O
STAUFR CONTNT I
STAUFR AT UPS I
STAUFR KANE LN
STAUFR IND OAK
WYOMNG/MULBR O
MULBRY N WASH O
MULBRY ADAMS I
MULBRY MADISN O
MULBRY MONROE O
MULBRY CLAY O
VINE N WEB
N WEB MULBRY
MULBRY N WEB O
MULBRY TAYLOR O
MULBRY N IRVG O
MULBRY PRSCT O
MULBRY HARRISN
MULBRY WHEELR O
MULBRY COLFX O
OLIVE COLFX O
OLIVE WHEELR O
OLIVE HARRISN O
OLIVE PRESCT O
PRESCT PINE O
PRESCT E GIBSN
PRESCT MYRTLE O
ASH PRESCOTT O
OLIVE WHEELR I
OLIVE COLFX I
PRESCT MYRTLE I
PRESCT E GIBSN
PRESCT PINE I
PRESCT OLIVE I
OLIVE HARRISN I
MULBRY COLFX I
MULBRY WHEELR I
MULBRY HARRISN
MULBRY PRESCT I
and 1174 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

11 findings, ordered by severity.

Show every finding

Warning5260 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 for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1822 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1424 instances
1424 of 1424 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning681 instances
681 of 681 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning104 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning6 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 for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1412 instances
About 1412 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info46 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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 72 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) Different (allowed): Your feed's agency_id is 0; your National Transit Database ID is 30025. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 0 to NTD ID 30025, and keep the feed value stable. Do not change it solely to make the two values equal.

shapes.txt covers your trips Ready: All 681 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 72 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.

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

Part of the Pennsylvania portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Pennsylvania

Other scorecards in Pennsylvania, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/"><img src="https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/badge.svg" width="320" height="58" alt="County of Lackawanna Transit System (COLTS): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![County of Lackawanna Transit System (COLTS): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/badge.svg)](https://gtfsscorecard.org/agency/county-of-lackawanna-transit-system-colts/)

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/county-of-lackawanna-transit-system-colts/2026-10-20.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-10-20. 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). County of Lackawanna Transit System (COLTS) GTFS feed-quality record, dated 2026-10-20 (grade D (63.6/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 c5aeb116a48a…). https://gtfsscorecard.org/data/artifacts/county-of-lackawanna-transit-system-colts/2026-10-20.json

@misc{gtfsscorecard-county-of-lackawanna-transit-system-colts-2026-10-20,
  title        = {County of Lackawanna Transit System (COLTS) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/county-of-lackawanna-transit-system-colts/2026-10-20.json}},
  note         = {Checked 2026-10-20; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (63.6/100)}
}

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