Turusi
manchu Banner army commander
Šongkoro Baturu Turusi (Manchu: ᡨᡠ᠋ᡵᡠᠰᡳ, romanized: Turusi, died 1634) was a Manchu military commander of the Plain Yellow Banner, belonging to the Irgen Gioro clan (alternatively recorded as the Šušu Gioro clan). In the service of the Manchu Khanate, he was frequently appointed as commander of frontline or elite reconnaissance forces Gabsihiyan and regarded as a “Champion of Valor” (驍勇冠軍), thus earning himself a Manchu warrior title Šongkoro Baturu (Manchu: ᡧᠣᠩᡴᠣᡵᠣᠪᠠᡨᡠᡵᡠ, Gyrfalcon Warrior).
Biography
Turusi joined Nurhaci's campaign along with his younger brother Fiyanggū from Yehe. In 1624, he was appointed a nirui janggin. Due to his success in pursuing deserters and suppressing banditry, he was promoted the following year to jalan i janggin and was granted the hereditary rank of adaha hafan.
In 1629, during the reign of Hong Taiji, Turusi accompanied the Qing campaign against the Ming dynasty and served as a frontline commander. During the Jisi Incident and the operations around Beijing, he proposed a raid at night against a Ming force of more than 40,000 troops stationed about 2 km south of Yongding Gate (永定門), and personally led it, being the first to break into the enemy garrison. His force killed the Ming commanders Man Gui and Sun Zushou (孫祖壽) in action, and captured the commanders Hei Yunlong (黑雲龍) and Ma Dengyun (麻登雲), thereby earning great distinction. In the following year (1630), Turusi was a part of Prince Abatai and Jirgalang's campaign against the rebel commander Liu Xingzuo (劉興祚), who was subsequently killed in battle. He later remained in defense of Yongping(永平) under Prince Amin.
Begin with the source’s own compact description: “Turusi” is manchu Banner army commander. The dossier treats that line as a proposition to test through Turusi, manchu and Banner, not as a finished interpretation.
Why this record matters
The phrase “manchu Banner army commander” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 6, 2026. The linked authority identifier is Q48927914. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1634, 1624, 1629 and 1630.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Turusi”, its source revision and the description used here.
- Expand the search: follow Turusi primary sources, Turusi archive and Turusi 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 “Turusi”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Turusi” 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.