Hegang
prefecture-level city in Heilongjiang, China
Hegang (Chinese: 鹤岗; pinyin: Hègǎng, also known as Heli and Xingshan) is a prefecture-level city in Heilongjiang province of China, situated in the southeastern section of the Lesser Khingan Range, facing Jiamusi across the Songhua River to the south and Russia's Jewish Autonomous Oblast across the Amur River to the north. Hegang is one of the principal coal-producing cities in China. Hegang covers an administrative area of 14,679.88 km2 (5,667.93 sq mi) and according to the 2020 Chinese census, has a population of 891,271 inhabitants, of whom 545,404 lived in the built-up (or metro) area made of 6 urban districts. By the end of 2024, the total registered population of the city was estimated at 935,000, including 756,000 in urban areas.
History
Early history
The region of Hegang was a desolate and uninhabited area until the late 1890s. In 1906, the area of Hegang City was under the administration of Tangyuan County under the Qing Dynasty. Since then, the government has been encouraging people to farm in the region. In 1914, a coalfield was discovered in Haoli, and Heilongjiang Government approved to set up Xinghua Mines (興華煤礦) which is jointly invested by merchants including Shen Songnian (沈松年). The area was also renamed Xingshan (興山) after the Xinghua Coal Mine. The Hegang mines were founded in 1916 by a Chinese entrepreneur with Russian capital.
The public source identifies “Hegang” as prefecture-level city in Heilongjiang, China. This brief keeps that definition visible, then builds a research path around Hegang, prefecture-level and city.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Hegang”, the useful work is to connect “prefecture-level city in Heilongjiang, China” to the records capable of establishing context and consequence.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Sep 12, 2026. The linked authority identifier is Q349982. VIAF identifies the subject as 126953826. The Library of Congress control number is no92011455. Authority coordinates are 47.314, 130.278. 4 of 6 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2020, 2024, 1906 and 1914.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Hegang”, its source revision and the description used here.
- Expand the search: follow Hegang primary sources, Hegang archive and Hegang research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Hegang”?
- Which earlier names or jurisdictions may reveal additional records?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Hegang” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.