GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Toei Subway (Tokyo Metropolitan Bureau of Transportation)

Based on the feed this agency publishes

Service mode Tram + Metro + Rail

81.7 / 100

First scorecard for this agency

Catalogued in Tokyo, Japan.

Covers 166 daysAccessibility gapsRealtime not yet published

The Toei subway network (Asakusa, Mita, Shinjuku, and Oedo lines); a distinct published feed from the Toei bus network, counted as one feed record.

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

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

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

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

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

Fix 03

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

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.

⏱ Often a bulk fix in your scheduling software.worth about +4 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.

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

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

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 166 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

Correctness92.0 / 100

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

Freshness100.0 / 100

Service data covers the next 166 days.

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.

1 accessibility depth signal

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (三田線, 大江戸線).

    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.

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

This feed has no route shapes, so the map shows its stops only.

Skip to route and stop data

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

Routes in Toei Subway (Tokyo Metropolitan Bureau of Transportation)'s feed
RouteTypeLine color
浅草線Subway / metropink (no shape in feed)
三田線Subway / metroteal (no shape in feed)
新宿線Subway / metroyellow (no shape in feed)
大江戸線Subway / metropink (no shape in feed)
日暮里・舎人ライナーRailpurple (no shape in feed)
東京さくらトラム（都電荒川線）Tram / light railred (no shape in feed)

This feed has 149 stops.

List every stop
  • 西馬込
  • 馬込
  • 中延
  • 戸越
  • 五反田
  • 高輪台
  • 泉岳寺
  • 三田
  • 大門
  • 新橋
  • 東銀座
  • 宝町
  • 日本橋
  • 人形町
  • 東日本橋
  • 浅草橋
  • 蔵前
  • 浅草
  • 本所吾妻橋
  • 押上
  • 目黒
  • 白金台
  • 白金高輪
  • 三田
  • 芝公園
  • 御成門
  • 内幸町
  • 日比谷
  • 大手町
  • 神保町
  • 水道橋
  • 春日
  • 白山
  • 千石
  • 巣鴨
  • 西巣鴨
  • 新板橋
  • 板橋区役所前
  • 板橋本町
  • 本蓮沼
  • 志村坂上
  • 志村三丁目
  • 蓮根
  • 西台
  • 高島平
  • 新高島平
  • 西高島平
  • 新宿
  • 新宿三丁目
  • 曙橋
  • 市ヶ谷
  • 九段下
  • 神保町
  • 小川町
  • 岩本町
  • 馬喰横山
  • 浜町
  • 森下
  • 菊川
  • 住吉
  • 西大島
  • 大島
  • 東大島
  • 船堀
  • 一之江
  • 瑞江
  • 篠崎
  • 本八幡
  • 新宿西口
  • 東新宿
  • 若松河田
  • 牛込柳町
  • 牛込神楽坂
  • 飯田橋
  • 春日
  • 本郷三丁目
  • 上野御徒町
  • 新御徒町
  • 蔵前
  • 両国
  • 森下
  • 清澄白河
  • 門前仲町
  • 月島
  • 勝どき
  • 築地市場
  • 汐留
  • 大門
  • 赤羽橋
  • 麻布十番
  • 六本木
  • 青山一丁目
  • 国立競技場
  • 代々木
  • 新宿
  • 都庁前
  • 西新宿五丁目
  • 中野坂上
  • 東中野
  • 中井
  • 落合南長崎
  • 新江古田
  • 練馬
  • 豊島園
  • 練馬春日町
  • 光が丘
  • 日暮里
  • 西日暮里
  • 赤土小学校前
  • 熊野前
  • 足立小台
  • 扇大橋
  • 高野
  • 江北
  • 西新井大師西
  • 谷在家
  • 舎人公園
  • 舎人
  • 見沼代親水公園
  • 三ノ輪橋
  • 荒川一中前
  • 荒川区役所前
  • 荒川二丁目
  • 荒川七丁目
  • 町屋駅前
  • 町屋二丁目
  • 東尾久三丁目
  • 熊野前
  • 宮ノ前
  • 小台
  • 荒川遊園地前
  • 荒川車庫前
  • 梶原
  • 栄町
  • 王子駅前
  • 飛鳥山
  • 滝野川一丁目
  • 西ヶ原四丁目
  • 新庚申塚
  • 庚申塚
  • 巣鴨新田
  • 大塚駅前
  • 向原
  • 東池袋四丁目
  • 都電雑司ヶ谷
  • 鬼子母神前
  • 学習院下
  • 面影橋
  • 早稲田

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

5 findings, ordered by severity.

Show every finding
  • Warning5600 instances

    5600 of 5600 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the transit vehicle 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

  • Warning149 instances

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

  • Warning3 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

  • 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.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

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 166 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 166 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 92 / 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 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.

Toei Subway (Tokyo Metropolitan Bureau of Transportation) GTFS data quality grade: B

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/toei-train/2026-07-18.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-18. 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.