Tokyo · JR East · 東日本旅客鉄道

山手線

Passenger service identity coverage

Current passenger services are separate from this source-defined statistical line and its historical observations.

No passenger service mapping is verified for this line. Coverage remains unresolved; no symbol is inferred from station numbers.

Identity methodology and limitations

Stations on this line

Latest published station value. The route-spine metric, period, source, and retrieval context are shown here; stations counted at a complex remain marked as such.

Metric: MLIT average daily entries and exits (operator station)
Unit: passengers_per_day
Reporting unit: operator station
Status: [reported]
Quality: [review needed]
Period: 2024-04-01 – 2025-03-31
Retrieved: 2026-09-14T12:42:54Z
Source: Ministry of Land, Infrastructure, Transport and Tourism (MLIT) · National Land Numerical Information — Station Passenger Counts

The operator does not publish a position for every station on this line, so this list is not a route order.

—
田端
Counted at the 田端 station complex.The operator publishes a single figure covering every platform in the complex, so 田端 has no separate figure. The complex total is not divided among its stations.
—
駒込87,080 [reported]
—
巣鴨134,320 [reported]
—
大塚108,702 [reported]
—
池袋
Counted at the 池袋 station complex.The operator publishes a single figure covering every platform in the complex, so 池袋 has no separate figure. The complex total is not divided among its stations.
—
目白67,082 [reported]
—
Takadanobaba高田馬場359,332 [reported]
—
新大久保98,492 [reported]
—
Shinjuku新宿JY17 Yamanote Line
Counted at the 新宿 station complex.The operator publishes a single figure covering every platform in the complex, so Shinjuku · 新宿 has no separate figure. The complex total is not divided among its stations.
—
Yoyogi代々木JY18 Yamanote Line
Counted at the 代々木 station complex.The operator publishes a single figure covering every platform in the complex, so Yoyogi · 代々木 has no separate figure. The complex total is not divided among its stations.
—
原宿134,814 [reported]
—
Shibuya渋谷648,828 [reported]
—
恵比寿252,020 [reported]
—
目黒186,768 [reported]
—
品川
Counted at the 品川 station complex.The operator publishes a single figure covering every platform in the complex, so 品川 has no separate figure. The complex total is not divided among its stations.
—
五反田220,642 [reported]
—
大崎290,388 [reported]

Station distribution

Where published station ridership is distributed on this line

One row represents one station, even where the published route lists it at more than one position. This is not a line total and station-complex figures are never allocated here.

Route order Ridership rank Change rank

新大久保98,492[reported]
恵比寿252,020[reported]
大塚108,702[reported]
原宿134,814[reported]
Shibuya渋谷648,828[reported]
目黒186,768[reported]
五反田220,642[reported]
Takadanobaba高田馬場359,332[reported]
巣鴨134,320[reported]
目白67,082[reported]
駒込87,080[reported]
大崎290,388[reported]

MLIT average daily entries and exits (operator station) · passengers per day · FY2024. Urban Rail Atlas analysis · [DERIVED]. Formula: (current − prior) / prior × 100; only consecutive fiscal years and non-zero prior values qualify.

Metric: MLIT average daily entries and exits (operator station)
Unit: passengers_per_day
Reporting unit: line station
Status: [reported]
Quality: [review needed]
Period: 2024-04-01 – 2025-03-31
Retrieved: 2026-09-14T12:42:54Z
Source: Ministry of Land, Infrastructure, Transport and Tourism (MLIT) · National Land Numerical Information — Station Passenger Counts

Exact station distribution values in change rank
Route position	Station	Operator	FY2024 value	Prior value	Change	Status / explanation
— Unknown	新大久保	JR East · 東日本旅客鉄道	98,492	93,452	▲ +5.4%	[reported]
— Unknown	恵比寿	JR East · 東日本旅客鉄道	252,020	242,206	▲ +4.1%	[reported]
— Unknown	大塚	JR East · 東日本旅客鉄道	108,702	104,504	▲ +4.0%	[reported]
— Unknown	原宿	JR East · 東日本旅客鉄道	134,814	129,970	▲ +3.7%	[reported]
— Unknown	Shibuya渋谷	JR East · 東日本旅客鉄道	648,828	628,118	▲ +3.3%	[reported]
— Unknown	目黒	JR East · 東日本旅客鉄道	186,768	181,204	▲ +3.1%	[reported]
— Unknown	五反田	JR East · 東日本旅客鉄道	220,642	215,278	▲ +2.5%	[reported]
— Unknown	Takadanobaba高田馬場	JR East · 東日本旅客鉄道	359,332	351,420	▲ +2.3%	[reported]
— Unknown	巣鴨	JR East · 東日本旅客鉄道	134,320	131,550	▲ +2.1%	[reported]
— Unknown	目白	JR East · 東日本旅客鉄道	67,082	65,746	▲ +2.0%	[reported]
— Unknown	駒込	JR East · 東日本旅客鉄道	87,080	85,438	▲ +1.9%	[reported]
— Unknown	大崎	JR East · 東日本旅客鉄道	290,388	375,884	▼ -22.7%	[reported]
— Unknown	Shinjuku新宿JY17 Yamanote Line	JR East · 東日本旅客鉄道	— No data published	— No data published	— Unavailable	Counted at the 新宿 station complex.The operator publishes a single figure covering every platform in the complex, so Shinjuku · 新宿 has no separate figure. The complex total is not divided among its stations.
— Unknown	Yoyogi代々木JY18 Yamanote Line	JR East · 東日本旅客鉄道	— No data published	— No data published	— Unavailable	Counted at the 代々木 station complex.The operator publishes a single figure covering every platform in the complex, so Yoyogi · 代々木 has no separate figure. The complex total is not divided among its stations.
— Unknown	品川	JR East · 東日本旅客鉄道	— No data published	— No data published	— Unavailable	Counted at the 品川 station complex.The operator publishes a single figure covering every platform in the complex, so 品川 has no separate figure. The complex total is not divided among its stations.
— Unknown	池袋	JR East · 東日本旅客鉄道	— No data published	— No data published	— Unavailable	Counted at the 池袋 station complex.The operator publishes a single figure covering every platform in the complex, so 池袋 has no separate figure. The complex total is not divided among its stations.
— Unknown	田端	JR East · 東日本旅客鉄道	— No data published	— No data published	— Unavailable	Counted at the 田端 station complex.The operator publishes a single figure covering every platform in the complex, so 田端 has no separate figure. The complex total is not divided among its stations.

Station concentration

No concentration result is shown for this line. Metro station-complex values cannot be allocated to member lines, so a line total or top-three share would be misleading.