GTFS Scorecard
← All agencies

Feed status · checked 2026-10-22

PAME Express (Lefkosia)

Based on the official feed source on file

Service mode Bus

78.5 / 100

unchanged since 2026-10-21

Cataloged in Lefkosia, Cyprus.

Covers 89 daysAccessibility gapsRealtime not yet published

Source feed: https://www.motionbuscard.org.cy/opendata/downloadfile?file=GTFS%5C11_google_transit.zip&rel=True Version history on the Mobility Database

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.

Checked for changes 30 minutes ago; last changed 6 hours ago.

Measured 3 of 4 score categories from the official feed URL on file.

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 official feed URL on file.

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

About this feed

PAME Express (Lefkosia)’s published feed lists 2 bus routes, 80 scheduled trips and 23 stops. Its service dates run from 2026-10-22 through 2027-01-19. The published file last changed on 2026-10-22.

Top things to fix

Fix 01

Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

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.

⏱ Varies.worth about +12 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

23 of 23 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 23 stops in the feed.

⏱ 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

80 of 80 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 80 trips in the feed.

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

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

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
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. Fix 01

    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. See this feed's finding-clearance log.

  2. Fix 02 · 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. See this feed's finding-clearance log.

  3. Fix 03 · 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. See this feed's finding-clearance log.

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 89 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 4 kinds of issue across 4 instances (1 error, 2 warning, 1 informational).

Freshness100.0 / 100

Service data covers the next 89 days.

Rider experience60.0 / 100

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

Accessibility0 / 100

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

1 accessibility depth signal

  • 11 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Archiep. Makariou III Ave. - Amaldas", "Archiep. Makariou III Ave. - Theofani Theodotou", "Archiep. Makariou III Ave. - Naxou", 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 23 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.

  • GSP1 (teal)
  • GSP1 (teal)
Routes in PAME Express (Lefkosia)'s feed
RouteTypeLine color
GSP1 GSP - Ministry of FinanceBusteal
GSP1 Ministry of Finance -Omirou - GSPBusteal
List every stop
  • Chilonos - Nechrou Avenue
  • Ave. Aigyptou - Omirou Avenue
  • Ministry of Finance
  • Archiep. Makariou III Ave. - Amaldas
  • Archiep. Makariou III Ave. - Theofani Theodotou
  • Archiep. Makariou III Ave. - Naxou
  • Archiep. Makariou III Ave. - Dimofontos
  • Technical School Nicosia I
  • Archiep. Makariou III Ave. - Ethnikis Frouras
  • Lemesou Ave. - Alpha Bank
  • Lemesou Ave. - San Sousi
  • Lemesou Ave. - Melkonian
  • Police Headquarters
  • Traffic Education Park
  • Lemesou Ave. - Ellispontou
  • Lemesou Ave. - Kalispera
  • Kinyra
  • Anexartisias Avenue - GSP
  • GSP Stadium
  • GSP Stadium
  • G. Leventi - Evagorou
  • Giannou Kranidioti - GSP 1
  • Giannou Kranidioti - GSP

Over time

Overall score across the last 21 checks — unchanged since 2026-10-21.

2026-10-02: 78.52026-10-03: 76.62026-10-04: 76.82026-10-05: 78.82026-10-06: 78.52026-10-07: 78.52026-10-08: 78.52026-10-09: 78.52026-10-10: 76.62026-10-11: 76.82026-10-12: 78.82026-10-13: 78.52026-10-14: 78.52026-10-15: 78.52026-10-16: 78.52026-10-17: 76.62026-10-18: 76.82026-10-19: 78.82026-10-20: 78.52026-10-21: 78.52026-10-22: 78.5
Show the numbers
CheckScoreChange
2026-10-0278.5 first check
2026-10-0376.6 down 1.9
2026-10-0476.8 up 0.2
2026-10-0578.8 up 2.0
2026-10-0678.5 down 0.3
2026-10-0778.5 no change
2026-10-0878.5 no change
2026-10-0978.5 no change
2026-10-1076.6 down 1.9
2026-10-1176.8 up 0.2
2026-10-1278.8 up 2.0
2026-10-1378.5 down 0.3
2026-10-1478.5 no change
2026-10-1578.5 no change
2026-10-1678.5 no change
2026-10-1776.6 down 1.9
2026-10-1876.8 up 0.2
2026-10-1978.8 up 2.0
2026-10-2078.5 down 0.3
2026-10-2178.5 no change
2026-10-2278.5 no change

What changed since your last check

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

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-224a709125ad7c2027-01-19Current rubric: see the trend above
2026-10-21ce67551aaf992027-01-18Current rubric: see the trend above
2026-10-20362dd0a567562027-01-17Current rubric: see the trend above
2026-10-19223384c588292027-01-15Current rubric: see the trend above
2026-10-1882f528a156ab2027-01-15Current rubric: see the trend above
2026-10-177e1b37f489f62027-01-14Current rubric: see the trend above
2026-10-16ce249c3833e72027-01-13Current rubric: see the trend above
2026-10-15fc7111804b402027-01-12Current rubric: see the trend above
2026-10-144e3f594b52652027-01-11Current rubric: see the trend above
2026-10-130893388a67302027-01-10Current rubric: see the trend above
2026-10-12531a059917d52027-01-08Current rubric: see the trend above
2026-10-11b6049f4ec08a2027-01-08Current rubric: see the trend above

Showing the 12 most recent of 86 periods.

What changed in this feed

Overall grade and score held steady since 2026-10-21.

The feed file was re-published since 2026-10-21.

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

Everything we checked

6 findings, ordered by severity.

Show every finding
  • Error1 instance

    Foreign key violation (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: foreign_key_violation · See MobilityData GTFS Validator rules

  • Warning80 instances

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

  • Warning23 instances

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

  • Warning1 instance

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

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

  • Warning1 instance

    Same name and description for stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules

  • Info1 instance

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

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 89 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 89 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.

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. 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.
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.
Rider experience 60 / 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.

Similar feeds in Lefkosia

Other scorecards in Lefkosia, 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.

PAME Express (Lefkosia): GTFS feed quality grade C, 78.5 of 100, checked 2026-10-22. GTFS Scorecard.

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/pame-express-lefkosia/2026-10-22.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-22. 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.