Asansol

Source identity and administrative path

The source row behind Asansol is GeoNames ID 1278314. Its recorded administrative path is Paschim Bardhaman → West Bengal → India, and GeoNames classifies the place as a second-order administrative seat. Āsansol occurs once as a primary city label in this atlas sample; the numeric ID remains the durable source key if names change.

The city row itself was updated 2024-01-06; that date belongs to the source record, not to every transport or visitor detail in the real destination.

Population position inside fixed cohorts

Within the fixed 1,206-record atlas, Asansol ranks 1,138 by recorded population. Inside the 109 selected India entries it ranks 103; inside the 632 entries in its broad region it ranks 599.

Its 504,271 population value is 0.50 times the 1,001,694 median for the country cohort and 0.50 times the 1,008,426 regional median. Asansol sits in the lower half of this atlas's selected India entries.

Asansol's recorded value is materially below the country-cohort median used here. These comparisons describe this selected dataset only; they are not current census rankings or official urban-area boundaries.

Nearest-reference pattern

Asansol's three nearest other atlas coordinates are Durgapur at 37.966 km with 518,872 recorded people; Dhanbad at 57.744 km with 1,196,214 recorded people; Bokaro at 84.713 km with 564,319 recorded people. The closest-to-farthest distance spread is 46.747 km. Compared with Durgapur, Asansol's recorded population is 0.97 times as large. Against Asansol, Durgapur follows Paschim Bardhaman → West Bengal → India in the source. Its point has lower latitude and higher longitude; it belongs to the same selected India cohort, uses the shared Asia/Kolkata identifier, and carries populated place rather than second-order administrative seat.

Its recorded population is above Asansol's. Against Asansol, Dhanbad follows Dhanbad → Jharkhand → India in the source. Its point has higher latitude and lower longitude; it belongs to the same selected India cohort, uses the shared Asia/Kolkata identifier, and carries the same second-order administrative seat class. Its recorded population is above Asansol's. Against Asansol, Bokaro follows Bokaro → Jharkhand → India in the source.

Its point has lower latitude and lower longitude; it belongs to the same selected India cohort, uses the shared Asia/Kolkata identifier, and carries the same second-order administrative seat class. Its recorded population is above Asansol's. Its nearest-neighbor distance ranks 351 of 1,206 from shortest to longest in the same snapshot. Asansol's nearest-coordinate gap sits in the second quarter of atlas distances. This pattern can reveal whether other catalog references are geographically close, but it cannot establish whether a border crossing is possible or practical, or whether rail, road, fare, or journey-time connections exist.

Read as one record signature, GeoNames 1278314, the coordinate pair 23.6833 / 86.9833, country rank 103 of 109, and neighbor GeoNames 1272175 at 37.966 km bind Asansol to a reproducible comparison. That combined key distinguishes the row; it is not a recommendation or evidence of a physical connection.

Coordinate, time-zone and class cohorts

Asansol's reference point is 23.6833° north and 86.9833° east. The IANA identifier Asia/Kolkata is shared by 109 city rows in this catalog, while the GeoNames class PPLA2 is shared by 341 rows. Asansol's row carries both second- and first-order administrative labels.

Asansol's point falls in the lower-latitude coordinate band used by this atlas's row checks. Asansol's time-zone field defines the narrower catalog cohort; its place class is shared more broadly. GeoNames supplies no elevation for Asansol, so the profile preserves that missing value instead of guessing terrain.

Together these fields form a reproducible identity check for this page, not a claim about walkability, climate or accessibility.