Salur (tribe)
Oghuz Turkmen tribe

Salur, Salyr or Salgur (Turkish: Salır, Turkmen: Salyr, سالؽر; Persian: سالور) was an ancient Oghuz Turkic (or Turkoman) tribe and a sub-branch of the Üçok tribal federation.
The medieval Karamanid principality in Anatolia belonged to the Karaman branch of the Salur. The Salghurids of Fars (Atabegs of Fars), were also a dynasty of Salur origin.
The patriarchs of the modern Turkmen tribe of the Salyr in Turkmenistan, Uzbekistan, Afghanistan, Iraq, and Iran, as well as the Salars of China, claim descent from the original Oghuz Salur.
Etymology
Historian and statesman of the Ilkhanate, Rashid al-Din Hamadani, in his literary work Oghuzname, which is part of his extensive history book Jami' al-tawarikh (Compendium of Chronicles), writes that the name Salyr means “wherever you go, you fight with a sword and a club”. The khan of the Khanate of Khiva and simultaneously a historian, Abu al-Ghazi Bahadur, in his Shajara-i Tarākima (Genealogy of the Turkmens) expresses his belief that the meaning of the tribe's name is “armed with a saber”.
Turkologist Peter B. Golden believes the name comes from Salğur < sal- "to put into motion, violent motion," in Oghuz "to be aggressive, to hurl oneself into attack." Thus, this is a tribal name expressing military power, force and aggression. Such nomenclature may have appeared more in the medieval Turkic environment (e.g. Qiniq), as for personal names.
History
According to various versions of the Oghuz Turkic heroic epos Oghuzname, the Salyr tribe played an important role in the Oghuz Yabgu State up to the middle of the 10th century until the beginning of the Seljuk movement, and many Khans of this State were from the Salyrs.
This brief starts where responsible research should: with the source description of “Salur (tribe)” as oghuz Turkmen tribe. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as oghuz Turkmen tribe. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 6, 2026. The linked authority identifier is Q1326317. None of the 0 selected statements returned an explicit reference.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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
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 “Salur (tribe)”, its source revision and the description used here.
- Expand the search: follow Salur (tribe) primary sources, Salur (tribe) archive and Salur 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 “Salur (tribe)”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Salur (tribe)” 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.