Feed status · checked 2026-07-24
Réseau urbain DK'BUS
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Hauts-de-France, France.
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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
757 of 790 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 +24 points in its category
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
9734 of 9734 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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.
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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 160 days.
- Published accessibility data
- Accessibility information is stated for 4.2% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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
The MobilityData validator flagged 5 kinds of issue across 11098 instances (0 error, 10955 warning, 143 informational).
Service data covers the next 160 days.
4% of stops state wheelchair accessibility (4% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
4% of stops state accessibility (4% marked accessible). Reflects what the feed states, not verified physical usability.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 16 (white)
- C2 (red)
- C1 (green)
- C3 (blue)
- C4 (orange)
- C5 (purple)
- 17 (yellow)
- 18 (white)
- 19 (brown)
- 20 (pink)
- 21 (teal)
- 24 (white)
- 23 (yellow)
- N1 (blue)
- N2 (teal)
- 26 (gray)
- S (black)
- 15 (gray)
- C6 (brown)
- RO (brown)
| Route | Type | Line color |
|---|---|---|
| 16 NAVETTE CENTRE VILLE | Bus | white |
| C2 LEFFRINCKOUCKE FORT DES DUNES - GRANDE-SYNTHE PUYTHOUCK | Bus | red |
| C1 LEFFRINCKOUCKE FORT DES DUNES - GRANDE-SYNTHE PUYTHOUCK | Bus | green |
| C3 LEFFRINCKOUCKE-PLAGE COUDEKERQUE - BRANCHE JARDINS DE STEENDAM | Bus | blue |
| C4 GRANDE-SYNTHE PUYTHOUCK - DUNKERQUE MALO PLAGE | Bus | orange |
| C5 DUNKERQUE FORT DE PETITE-SYNTHE - DUNKERQUE MARAICHERS | Bus | purple |
| 17 GRANDE SYNTHE PUYTHOUCK - COUDEKERQUE-BRANCHE VILLAGE | Bus | yellow |
| 18 GRANDE-SYNTHE PUYTHOUCK - COUDEKERQUE-VILLAGE BOIS DES FORTS | Bus | white |
| 19 GRANDE-SYNTHE PUYTHOUCK - DUNKERQUE GARE | Bus | brown |
| 20 LEFFRINCKOUCKE FORT DES DUNES-FRONTIERE - ADINKERQUE | Bus | pink |
| 21 GHYVELDE LES MOERES - FORT DES DUNES | Bus | teal |
| 24 NAVETTE FORT DES DUNES | Bus | white |
| 23 GRAVELINES - BOURBOURG - GRANDE-SYNTHE | Bus | yellow |
| N1 GRANDE-SYNTHE PUYTHOUCK - LEFFRINCKOUCKE FORT DES DUNES | Bus | blue |
| N2 CAPPELLE-LA-GRANDE CROIZAT - TETEGHEM VANDERMEERSCH | Bus | teal |
| 26 GRAND-FORT-PHILIPPE - GRAVELINES - PETIT-FORT-PHILIPPE | Bus | gray |
| S | Bus | black |
| 15 GRANDE-SYNTHE PUYTHOUCK - DUNKERQUE GARE | Bus | gray |
| C6 CAPPELLE-LA-GRANDE CROIZAT - TETEGHEM VANDERMEERSCH CIMETIERE | Bus | brown |
| RO RAPID OUEST DUNKERQUE GARE - POLE INTERMODALE BOURBOURG GARE | Bus | brown |
This feed has 790 stops.
List every stop
- NOORDOVER
- PAPIN
- PAPIN
- PASTEUR
- PASTEUR
- DUNKERQUE MALO PLAGE
- DUNKERQUE MALO PLAGE
- CURIE
- CURIE
- PARC DES SPORTS
- PARC DES SPORTS
- PARC DES SPORTS
- PARC DES SPORTS
- PERES
- PERES
- PEUPLIERS
- PEUPLIERS
- VICTOR HUGO
- VICTOR HUGO
- PICASSO
- PICASSO
- PICARDIE
- PICARDIE
- DUNKERQUE MALO PLAGE
- DUNKERQUE MALO PLAGE
- PLAINES DU NORD
- PLANTIS
- PLACE DE L'ABBE PIERRE
- PLACE DE L'ABBE PIERRE
- PLET
- PLET
- PALAIS DU LITTORAL
- PALAIS DU LITTORAL
- BEFFROI
- BEFFROI
- PLACE REPUBLIQUE
- PLACE REPUBLIQUE
- PLACE REPUBLIQUE
- PLACE D'UXEM
- PAUL MACHY
- PAUL MACHY
- MARDYCK ROUTE DES DUNES
- MARDYCK ROUTE DES DUNES
- PARC MARINE
- PARC MARINE
- POLYCLINIQUE
- POLYCLINIQUE
- POMPIERS
- POMPIERS
- PORT FLUVIAL
- PORT FLUVIAL
- PRANARD
- PRANARD
- PROGRES
- PROGRES
- PROGRES
- PAUL BERT
- PAUL BERT
- PONT A CHARETTES
- PONT A CHARETTES
- PONT AU COQ
- PONT AU COQ
- PONT LOBY
- PONT LOBY
- PONT NEUF
- RABELAIS
- RABELAIS
- LYCEE EUROPE
- LYCEE EUROPE
- RUE DU LAC
- RUE DU LAC
- RUE DE LA GARE
- RUE DE LA GARE
- RUE DE LILLE
- RUE DE LILLE
- RUE DU MOULIN
- RUE DU MOULIN
- RUE DU MOULIN
- RUE DU NORD
- RUE DU NORD
- ECOPARC
- ECOPARC
- REPUBLIQUE
- REPUBLIQUE
- RESISTANCE
- RESISTANCE
- OYATS
- OYATS
- REYNAERT
- REYNAERT
- RIGAUD
- RIGAUD
- DUNKERQUE MARAICHERS
- ROYER
- ROYER
- ROYER
- ROYER
- ROMAIN ROLLAND
- ROMAIN ROLLAND
- ROMAIN ROLLAND
- ROMAIN ROLLAND
- ROUTE DE BOURBOURG
- ROUTE DE BOURBOURG
- ROUTE DE COUDEKERQUE
- ROUTE DE COUDEKERQUE
- ROUTE D`UXEM
- ROUTE D`UXEM
- RUSSEL
- RUSSEL
- SABLIERE
- SABLIERE
- SAMARITAINE
- SAMARITAINE
- LES SAVANTS
- LES SAVANTS
- MAGASIN GENERAL
- SCHWEITZER
- SCHWEITZER
- SCIERIES
- SCIERIES
- ILE JEANTY
- ILE JEANTY
- PORTE DU SOLEIL
- PORTE DU SOLEIL
- COMTE JEAN
- COMTE JEAN
- BABOEUF
- SORBIERS
- SORBIERS
- CIMETIERE SAINT POL
- CIMETIERE SAINT POL
- SAINT BENOIT
- SAINT BENOIT
- MAIRIE SAINT POL
- MAIRIE SAINT POL
- SPORTICA
- SPORTICA
- RAFFINERIE
- RAFFINERIE
- STADE TRIBUT
- STADE TRIBUT
- SAINT ANTOINE
- SAINT ANTOINE
- FORT LOUIS
- FORT LOUIS
- SAINTE CATHERINE
- SAINTE CATHERINE
- COUDEKERQUE BRANCHE STEENDAM
- COUDEKERQUE BRANCHE STEENDAM
- COUDEKERQUE BRANCHE STEENDAM
- SAINTE GERMAINE
- DE LA SALLE
- SAINTE GERMAINE
- MAIRIE SAINT GEORGES
- MAIRIE SAINT GEORGES
- SAINT JACQUES
- SAINT JACQUES
- SAINT JEAN BAPTISTE
- SAINT JEAN BAPTISTE
- SAINT NICOLAS
- SAINT NICOLAS
- STRASBOURG
- STRASBOURG
- TENNIS
- TENNIS
- TENTE VERTE
- TENTE VERTE
- VANCASSEL
- SAINT PIERRE
- SAINT PIERRE
- PHARES ET BALISES
- PHARES ET BALISES
- TLEGERVELD
- TLEGERVELD
- TRIANGLE
- TRIANGLE
- TRISELEC
- TRISELEC
- DUINSTRAAT
- DUINSTRAAT
- TRYSTRAM
- TRYSTRAM
- TURENNE
- TURENNE
- UNIVERSITE
- UNIVERSITE
- TETEGHEM VANDERMEERSCH
- TETEGHEM VANDERMEERSCH
- VAUBAN
- VERDUN
- VERDUN
- VERLOMME
- VERLOMME
- VERT GAZON
- VERT GAZON
- VICTOIRE
- VICTOIRE
- VOLTAIRE
- VOLTAIRE
- WALCKER
- WALCKER
- WEILL
- WEILL
- WESTHOEK
- WESTHOEK
- BANC VERT
- BANC VERT
- ZONE INDUSTRIELLE
- ZONE INDUSTRIELLE
- CAMPING ZUYDCOOTE
- MAIRIE ZUYDCOOTE
- MAIRIE ZUYDCOOTE
- MICHELET
- MICHELET
- REPDYCK
- REPDYCK
- BIBLIOTHEQUE COUDEKERQUE VILLAGE
- BIBLIOTHEQUE COUDEKERQUE VILLAGE
- CARREFOUR DU LOUP
- QUAI DE LA COLME
- QUAI DE LA COLME
- ABBE PAREZYS
- ABBE PAREZYS
- MAIRIE SPYCKER
- MAIRIE SPYCKER
- GRAND MILLEBRUGGHE
- LE LAC
- HOOGHEPORTE
- HOOGHEPORTE
- LE LAC
- PONT DE GHYVELDE
- PONT DE GHYVELDE
- SANGLIERS
- SANGLIERS
- PLACE DU BERCK
- PLACE DU BERCK
- SOGELOGE
- SOGELOGE
- GHYVELDE LAC DES HERONS
- GHYVELDE LAC DES HERONS
- DANY BOON
- DANY BOON
- POSTE BRAY DUNES
- PISCINE BOURBOURG
- PISCINE BOURBOURG
- GARE GRAVELINES
- ILE JEANTY
- LEFFRINCKOUCKE FORT DES DUNES
- LEFFRINCKOUCKE FORT DES DUNES
- ROBINSON
- and 540 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
- Warning10137 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9734 instances
9734 of 9734 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning816 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning757 instances
757 of 790 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)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Validator rule: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · 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)
- Info776 instances
About 776 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.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info143 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Validator rule: big_gap_in_service · 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.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 4% 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 160 days.
- Accessible Not yet
- States wheelchair access on 4% 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 160 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. Read the full standards crosswalk.
- Correctness 75 / 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 85 / 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 24 / 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.
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/fr-pan-82683/2026-07-24.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-07-24. 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.