Šinahuttum
Possible ancient city in Assyria
Šinahuttum, later known as Sanahuitta, was a Bronze Age Assyrian city believed to have been northeast of Hattusa, the capital of the Hittite Empire in the late Bronze Age, near modern Boğazkale in Turkey. The city is mentioned in Assyrian sources 14 times and was noted for its donkey market and wool exchange.
Location
The likely location of Šinahuttum was identified by historians using statistical methods to interrogate the records of merchants found at Kaneš near the modern Turkish city of Kayseri.
The site in early times
It was mentioned first as Sinahuttum in the Assyrian Colony text C18, along with other cities as Ankuwa and Kapitra which rebelled against Hattusa in Late Bronze Age period. It was part of the Hittite kingdom, as is commented in text C17.
In early times, king Labarna I was the sovereign of the small city-state of Kussara, who during his campaigns to enlarge his territory went to the northeast of Kussara and conquered the city-state of Sanahuitta. Then he set up one of his sons as governor of the city, but the inhabitants rebelled and elected Papahdilmah as their authority. After Papahdilmah took the throne of Samahuitta in a coup, the Hittite state was divided in two, with one faction ruling from Samahuitta and the other controlling the southern territory from Kussara. Sanahuitta was apparently independent until Hattusili I, in his first campaign, sacked the surrounding territory, but not conquered the city itself, what he did three years later, after a siege of six months.
The public source identifies “Šinahuttum” as possible ancient city in Assyria. This brief keeps that definition visible, then builds a research path around Šinahuttum, Possible and ancient.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Šinahuttum”, the useful work is to connect “possible ancient city in Assyria” to the records capable of establishing context and consequence.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Jul 18, 2026. The linked authority identifier is Q391125. Authority coordinates are 40.020, 34.615. None of the 1 selected statements returned an explicit reference.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. 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 “Šinahuttum”, its source revision and the description used here.
- Expand the search: follow Šinahuttum primary sources, Šinahuttum archive and Šinahuttum 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 “Šinahuttum”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Šinahuttum” 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.