Siege of Seringapatam (1639)
conflict in India

The siege of Seringapatam in 1639 was a conflict between the Bijapur Sultanate's forces, led by Randaula Khan and the Mysorean army commanded by Kanthirava Narasaraja I. The Bijapur army had laid siege to the Seringapatam Fort, but Kanthirava Narasaraja I mounted a daring night attack on their encampment. The surprise assault overwhelmed the Bijapur forces, resulting in their defeat. Following this victory, the Mysorean army triumphantly returned to the Srirangapatna fort.
Background
Kanthirava Narasaraja I incitement of Elenge Hanuma of Basavapatna and other Wodeyars of Ikkeri against their liege lord, Virabhadra Nayaka, led to a brief but intense disturbance in the region. However, the Ikkeri Nayaka swiftly quelled the rebellion, maintaining his control. Undeterred, Kenge Hanuma traveled to Bijapur, seeking the Sultan's aid. Meanwhile, Channama, a fugitive Wodeyar from Nagamangala, recently conquered by Chamaraja Wodeyar VI, also sought refuge with the Sultan. In response, the Sultan dispatched his most reputed general, Randaula Khan, leading an army of forty thousand men, with the mission to restore Kenge Hanuma to power and, if possible, seize Srirangapatna from the Wodeyars.
Planning
Randaula Khan after receiving the Sultan's orders, focused his efforts on the conquest of Srirangapatna, recognizing that capturing the city would be crucial for weakening the Wodeyars' hold over their territories. Aware that seizing the capital would not be an easy task, he carefully planned his approach, considering various strategies to bring the ruling forces under control.
The public source identifies “Siege of Seringapatam (1639)” as conflict in India. This brief keeps that definition visible, then builds a research path around Siege, Seringapatam and conflict.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Siege of Seringapatam (1639)”, the useful work is to connect “conflict in India” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q131418149. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1639.
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 “Siege of Seringapatam (1639)”, its source revision and the description used here.
- Expand the search: follow Siege of Seringapatam (1639) primary sources, Siege of Seringapatam (1639) archive and Siege 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 “Siege of Seringapatam (1639)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Siege of Seringapatam (1639)” 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.