Suhaldev
legendary Indian king
Suhaldev was a legendary king from Shravasti town of India. Persian hagiography Mirat-i-Masudi, written in 17th century, popularly mentions him to have defeated and killed the Ghaznavid general Ghazi Saiyyad Salar Masud at Bahraich in 1034 CE. He was killed by Syed Ibrahim, a commander of Salar Masud.
Sources
During the reign of Jahangir (r. 1605–1627), Abd-ur-Rahman Chishti penned Mirat-i-Masudi, a Persian hagiography in praise of Ghazi Miyan, a Turkic commander. It is doubtful whether Miyan existed at all but he was already occupying a prominent spot-of-veneration in public memory as a quasi-mythic warrior-saint and Chisti accentuated the process, employing an imaginary past.
Suhaldev is mentioned in the same chronicles, as the eldest son of King Mordhwaj of Shravasti and Miyan's chief antagonist in the Bahraich region.
Legend
In different versions of the legends, Suhaldev is known by different names, including Sakardev, Suhirdadhwaj, Suhridil, Suhridal-dhaj, Rai Suhrid Dev, Susaj, Suhardal, Sohildar, Shahardev, Sahardev, Suhar Deo, Sahar Deo, Suhaaldev, Suhildev, Suheldev, Sohal Deo and Suheldeo.
Ghazi Miyan, after his initial invasions established his capital at Satrikh and then, dispatched an army to defeat the local king. Despite defeating the local Raja of Bahraich (who had even formed a confederation with other Hindu kings) under the commandeering of his father, his rule was continuously threatened by the Rajahs. Therefore, in 1033 CE, Miyan himself arrived in Bahraich to check their advance and re-defeated his enemies, until the arrival of Suhaldev.
Begin with the source’s own compact description: “Suhaldev” is legendary Indian king. The dossier treats that line as a proposition to test through Suhaldev, legendary and Indian, not as a finished interpretation.
Why this record matters
The phrase “legendary Indian king” 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.
Chronology provides the most reliable spine for this subject; interpretation should follow only after identities and dates are secure. The source revision retrieved here is dated Jul 18, 2026. The linked authority identifier is Q7285556. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1034, 1605, 1627 and 1033.
A concise life account rarely captures disputed attribution, private networks or the changing language used to describe a career. 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
Read biographical claims against dates, named institutions and the cited references. Distinguish a subject’s later reputation from evidence produced during their lifetime.
- Establishing names and roles
- Building a first chronology
- Locating cited institutions
Personal papers, civil or court records, institutional files and the scholarship cited by the source.
Three-step research path
- Establish the record: confirm the title “Suhaldev”, its source revision and the description used here.
- Expand the search: follow Suhaldev primary sources, Suhaldev archive and Suhaldev 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 “Suhaldev”?
- How has the subject’s reputation changed across later accounts?
- Which primary records establish identity, chronology and institutional ties?
Search terms from this dossier
This entry incorporates text from “Suhaldev” 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.