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.

—
日進24,980 [reported]
—
西大宮25,212 [reported]
—
西川越2,588 [reported]
—
的場6,102 [reported]
—
指扇19,130 [reported]
—
笠幡5,648 [reported]
—
川越72,160 [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.
—
南古谷15,924 [reported]
—
武蔵高萩6,440 [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.

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

西大宮25,212[reported]
笠幡5,648[reported]
武蔵高萩6,440[reported]
川越72,160[reported]
指扇19,130[reported]
日進24,980[reported]
南古谷15,924[reported]
的場6,102[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 · 東日本旅客鉄道	25,212	24,198	▲ +4.2%	[reported]
— Unknown	笠幡	JR East · 東日本旅客鉄道	5,648	5,504	▲ +2.6%	[reported]
— Unknown	武蔵高萩	JR East · 東日本旅客鉄道	6,440	6,284	▲ +2.5%	[reported]
— Unknown	川越	JR East · 東日本旅客鉄道	72,160	70,588	▲ +2.2%	[reported]
— Unknown	指扇	JR East · 東日本旅客鉄道	19,130	18,734	▲ +2.1%	[reported]
— Unknown	日進	JR East · 東日本旅客鉄道	24,980	24,546	▲ +1.8%	[reported]
— Unknown	南古谷	JR East · 東日本旅客鉄道	15,924	15,746	▲ +1.1%	[reported]
— Unknown	的場	JR East · 東日本旅客鉄道	6,102	6,104	▼ -0.0%	[reported]
— 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	2,588	— Unavailable	No compatible value was published for FY2024.
— 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.