Burmese–Siamese War (1792–1794)
1792-1794 war
The Burmese–Siamese War (1792–1794) or the Siamese Invasion of Tavoy was the conflict between the Kingdom of Burma under Konbaung dynasty and the Kingdom of Siam under the Chakri dynasty over the town of Tavoy and the Tenasserim Coast.
Siam under King Rama I attempted to claim the Tenasserim Coast and the towns of Tavoy and Mergui, which were former possessions of Siam during the times of Kingdom of Ayutthaya. The defection of Burmese governor of Tavoy to Siam in March 1792 gave Siam an opportunity to realize the goals. With Tavoy and Mergui under control, King Rama I planned an expedition into Lower Burma. However, King Bodawpaya of Burma, aiming to keep the Tenasserim Coast in Burmese control, sent his son Prince Thado Minsaw to counter Siamese offensives. The Siamese were soundly defeated in the Battle of Tavoy in January 1794 and retreated.
Background
The Tenasserim Coast had been battlegrounds of the vying for control between Burma and Siam since the sixteenth century. Tenasserim Coast consisted of two parts; the northern part centered on the town of Tavoy and the southern part centered on the town of Tanintharyi (Thai: ตะนาวศรี, RTGS: Tanao Si). At the mouth of the Tenasserim River laid the port city of Mergui, which was an important Siamese trading port during the reign of King Narai. The Tenasserim Coast was known as "Tavoy, Mergui and Tenassserim" in Thai sources.
Begin with the source’s own compact description: “Burmese–Siamese War (1792–1794)” is 1792-1794 war. The dossier treats that line as a proposition to test through Burmese, Siamese and 1792-1794, not as a finished interpretation.
Why this record matters
The phrase “1792-1794 war” 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 record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q104901667. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1792 and 1794.
Official terminology may obscure informal participation, dissent or communities documented only indirectly. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Burmese–Siamese War (1792–1794)”, its source revision and the description used here.
- Expand the search: follow Burmese–Siamese War (1792–1794) primary sources, Burmese–Siamese War (1792–1794) archive and Burmese 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 “Burmese–Siamese War (1792–1794)”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Burmese–Siamese War (1792–1794)” 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.