Date confidence
Exact dates are used only where records support them. “Approximate” preserves a range or scholarly estimate rather than manufacturing a single year.

Evidence-led historical discovery
Explore documented battles, sieges, campaigns and resistance across Tamil Nadu through time and place.
Editorial visual · My Tamil Nadu editorial studio · Original project artwork; not documentary evidence or a reconstruction of one eventAbout this collection
This hub covers documented armed conflicts and resistance events whose locations fall within present-day Tamil Nadu. Its chronology runs from early medieval dynastic contests to the Vellore uprising of 1806. “Conflict” here includes battles, sieges and rebellion; it does not imply that every event had the same scale, causes or historical meaning.
Historical records are uneven. Some dates are exact while others are approximate ranges. A modern town can be securely identified even when the boundary of a battlefield is not. The three confidence labels on every record keep date, location and event evidence separate.
Chronological discovery
Search names and places or combine a period, conflict type, political power and modern district. Filtering changes only this page and creates no separate search routes.
Try a broader search or remove one of the filters.
Pallava sources and later scholarship place a Pallava victory over Chalukya forces at Manimangalam.
Participants: Pallava kingdom and Western Chalukya kingdom
Outcome: Pallava victory in the Tamil theatre.
Why it mattered: A securely place-linked Pallava conflict near Kanchipuram.
Pallava kingdom (kingdom); Western Chalukya kingdom (kingdom)
Narasimhavarman I; Pulakeshin II; Paranjothi (associated in later campaign sequence)
Part of the sequence that preceded the Pallava advance to Vatapi.
inscription, scholarly reconstruction. University histories cite the Kuram plates and established Pallava scholarship.
Modern town identification is stable; battlefield limits are not established.
town/locality; no verified battlefield interpretation recorded. Use the modern town only as orientation; do not imply a marked battlefield.
Nandivarman III's victory at Tellaru became a central element of his royal titulature.
Participants: Pallava kingdom and Pandya-led forces
Outcome: Pallava victory.
Why it mattered: Combines literary praise with inscriptions that preserve the victor's Tellaru title.
Also known as: Battle of Thellar
Pallava kingdom (kingdom); Pandya-led forces (kingdom/confederacy)
Nandivarman III
Checked the northward Pandya advance and reinforced Nandivarman's authority.
inscription, literary tradition, scholarly reconstruction. Pallava inscriptions and Nandikkalambakam references converge on the event.
Scholarly identification places Tellaru in former Wandiwash taluk.
modern town; precise field unverified. No public-access battlefield claim should be made without a site survey.
A coalition associated with Aparajita and Aditya I defeated Pandya forces near Tiruppurambiyam.
Participants: Pallava-Chola-Ganga alliance and Pandya forces
Outcome: Coalition victory over the Pandyas.
Why it mattered: A major political turning point in the Kaveri delta.
Also known as: Battle of Sripurambiyam
Pallava-Chola-Ganga alliance (confederacy); Pandya forces (kingdom)
Aparajita Pallava; Aditya I; Varaguna II
Contributed to Chola ascendancy, though it did not alone cause the transition.
inscription, later historical text, scholarly reconstruction. University histories synthesize epigraphic and dynastic evidence while differing on exact year.
Town identification is stable; date varies across summaries.
village and temple landscape; battlefield interpretation unverified. Do not promise visible battlefield remains.
Krishna III's forces defeated the Chola side at Takkolam; Rajaditya died in the battle tradition.
Participants: Chola kingdom and allies and Rashtrakuta kingdom and allies
Outcome: Rashtrakuta victory.
Why it mattered: One of the best-attested battle sites in medieval Tamil political history.
Chola kingdom and allies (kingdom/confederacy); Rashtrakuta kingdom and allies (kingdom/confederacy)
Parantaka I; Krishna III; Rajaditya (Chola prince)
Chola control in the north weakened for a period.
inscription, scholarly reconstruction. Dynastic inscriptions and standard scholarship support the event, date and political result.
Modern Takkolam near Arakkonam is the accepted identification.
modern settlement; battle interpretation not audited. Modern-place orientation only until a defensible battlefield boundary is sourced.
Travancore defeated Dutch forces at Colachel in 1741.
Participants: Kingdom of Travancore and Dutch East India Company
Outcome: Travancore victory and Dutch prisoners.
Why it mattered: A well-located conflict connecting present Kanniyakumari district to Travancore and European colonial history.
Also known as: Battle of Kulachal
Kingdom of Travancore (kingdom); Dutch East India Company (colonial power/company army)
Marthanda Varma; Eustachius De Lannoy
Reduced Dutch political leverage in the region; De Lannoy later served Travancore.
colonial archival record, government/institutional historical account, scholarly reconstruction. Government accounts and extensive Travancore scholarship agree on place, year and principal outcome.
Modern coastal town identification is certain; exact battle footprint includes land and maritime dimensions.
coastal town with memorial tradition. Town and memorial context only; verify access separately in a future travel layer.
Maratha forces besieged and captured Trichinopoly; Chanda Sahib was taken prisoner.
Participants: Maratha forces and Chanda Sahib's Carnatic forces
Outcome: Maratha capture and Chanda Sahib's imprisonment.
Why it mattered: A major pre-Carnatic-War siege at a site central to later conflict.
Also known as: Capture of Trichinopoly, 1741
Maratha forces (confederacy/army); Chanda Sahib's Carnatic forces (local ruler/army)
Chanda Sahib; Raghuji Bhonsle; Fateh Singh Bhonsle
Reshaped the Carnatic succession before the Anglo-French wars.
colonial archival record, later historical text, scholarly reconstruction. Archival catalogues and regional histories preserve the siege and surrender.
Fort-city identification is certain; individual siege lines require later mapping.
major city and fort-temple landscape. Rock Fort is an urban heritage area; no access promise.
The coalition supporting Chanda Sahib defeated Anwar-ud-din at Ambur; Anwar-ud-din was killed.
Participants: Anwar-ud-din's Carnatic forces and Chanda Sahib, Muzaffar Jang and French allies
Outcome: Coalition victory.
Why it mattered: A clear place-based turning point in Carnatic succession politics.
Anwar-ud-din's Carnatic forces (kingdom/army); Chanda Sahib, Muzaffar Jang and French allies (confederacy)
Anwar-ud-din Khan; Chanda Sahib; Muzaffar Jang
Opened a new phase of the Second Carnatic War.
colonial archival record, near-contemporary chronicle, scholarly reconstruction. British Library holdings include near-contemporary Arcot histories describing the overthrow of Anwar-ud-din.
Town identification is secure; battlefield extent not yet sourced.
modern town; battlefield remains unverified. Modern town only; no verified battlefield visitor site.
A prolonged sequence of siege, blockade and relief actions centred on the fortified city and Srirangam island.
Participants: Muhammad Ali and East India Company allies and Chanda Sahib and French allies
Outcome: Company-backed side retained Trichinopoly; Chanda Sahib's cause collapsed.
Why it mattered: Best modelled as a parent campaign with several child engagements.
Also known as: Trichinopoly campaign
Muhammad Ali and East India Company allies (confederacy); Chanda Sahib and French allies (confederacy)
Muhammad Ali Khan Wallajah; Chanda Sahib; Stringer Lawrence; Jacques-Francois Law
Helped establish Muhammad Ali and British influence in the Carnatic.
colonial archival record, contemporary/near-contemporary chronicle, scholarly reconstruction. British Library Orme papers include narratives and correspondence specifically covering Trichinopoly, 1751-1754.
Multi-location campaign; must not be reduced to one battlefield marker.
major city, fort-temple landscape and inhabited island. Multiple urban and sacred places; military history must not subsume living temple context.
A Company-led garrison held Arcot against a prolonged siege by Chanda Sahib's coalition.
Participants: East India Company and Muhammad Ali's supporters and Chanda Sahib's forces and French allies
Outcome: Siege lifted after failed assaults.
Why it mattered: A central, archive-rich episode of the Second Carnatic War.
Also known as: Defence of Arcot
East India Company and Muhammad Ali's supporters (company army/confederacy); Chanda Sahib's forces and French allies (confederacy)
Muhammad Ali Khan Wallajah; Chanda Sahib; Robert Clive; Raza Sahib
Strengthened the Company-backed claimant and British reputation in the Carnatic.
colonial archival record, government/institutional historical account, scholarly reconstruction. India Office records and municipal history support the place and campaign context.
Town and fort context are secure; much of the historical fort has changed.
historic town with fragmentary fort context. Present-day fort remains and Delhi Gate require separate heritage/access verification.
A night engagement near Kaveripakkam ended in a Company-backed victory.
Participants: East India Company and Muhammad Ali's supporters and French and Chanda Sahib's supporters
Outcome: Company-backed victory.
Why it mattered: A distinct northern Tamil battle in the Second Carnatic War.
Also known as: Battle of Kaveripakkam
East India Company and Muhammad Ali's supporters (company army/confederacy); French and Chanda Sahib's supporters (confederacy)
Muhammad Ali Khan Wallajah; Chanda Sahib; Robert Clive
Reduced French-aligned pressure in the Arcot theatre.
colonial archival record, scholarly reconstruction. Campaign correspondence and established Carnatic War histories support the event.
Modern town identification is secure; field location needs source-level mapping.
modern town and surrounding landscape. No verified visitor site.
French forces besieged Fort St George but withdrew without taking it.
Participants: French East India Company and allied forces and British East India Company garrison and allies
Outcome: Siege failed.
Why it mattered: A major conflict at the core of modern Chennai's colonial district.
Also known as: Siege of Fort St George
French East India Company and allied forces (colonial power/company army); British East India Company garrison and allies (company army/confederacy)
Thomas Arthur de Lally; William Draper
Preserved the British base before the Wandiwash campaign.
colonial archival record, government/institutional historical account, scholarly reconstruction. Digitised institutional histories and extensive Company/French archives document the siege.
Fort location is exact; siege operations extended across surrounding settlements.
active government and heritage precinct. Fort St George is an active government/security complex; access cannot be assumed.
Company forces under Eyre Coote defeated the French field army near Wandiwash.
Participants: British East India Company and allies and French East India Company and allies
Outcome: British Company victory.
Why it mattered: A decisive and well-located battle in colonial South Indian history.
Also known as: Battle of Vandavasi
British East India Company and allies (company army/confederacy); French East India Company and allies (company army/confederacy)
Eyre Coote; Thomas Arthur de Lally; Comte de Bussy
Severely weakened French military power in the Carnatic, followed by the fall of Pondicherry.
colonial archival record, government archaeological account, scholarly reconstruction. Tamil Nadu Archaeology preserves the fort context and commemorative inscription; archival histories confirm the battle.
Town and fort identification are secure; exact field extent should be sourced separately.
fort remains and modern town. Fort remains are protected heritage; verify current access separately.
Mysore forces defeated and captured much of Baillie's detachment at Pollilur.
Participants: Kingdom of Mysore and British East India Company force
Outcome: Major Mysore victory.
Why it mattered: A major Company defeat with rich visual and archival afterlives.
Also known as: Baillie's defeat at Pollilur
Kingdom of Mysore (kingdom); British East India Company force (company army)
Hyder Ali; Tipu Sultan; Tipu Sultan; William Baillie
Placed the Madras government in a critical position but did not decide the war.
colonial archival record, contemporary journal, Mysore court tradition, museum interpretation. National Army Museum synthesis and contemporary journals establish the event and campaign significance.
Published spelling and modern-locality mapping need a dedicated gazetteer check before coordinates.
rural/locality context; exact interpretation unverified. Do not map until Pollilur/Pullalur locality identification is reconciled.
Eyre Coote's army defeated Hyder Ali's forces near Porto Novo.
Participants: British East India Company and allies and Kingdom of Mysore
Outcome: Company victory.
Why it mattered: A major Second Anglo-Mysore War engagement on the Cuddalore coast.
Also known as: Battle of Parangipettai
British East India Company and allies (company army/confederacy); Kingdom of Mysore (kingdom)
Hyder Ali; Eyre Coote; Hyder Ali
Stabilised the Company position but did not end the war.
colonial archival record, government district gazetteer, scholarly reconstruction. Institutional histories record Coote's victory; district gazetteer anchors Porto Novo/Parangipettai.
Historical and modern town equivalence is secure; exact battle line remains unmapped.
coastal town and surrounding landscape. Working coastal town; no access or remains claim.
Coote's forces defeated Mysore's army near Sholinghur.
Participants: British East India Company and allies and Kingdom of Mysore
Outcome: Company victory.
Why it mattered: A clear northern Tamil Nadu site in the Second Anglo-Mysore War.
Also known as: Battle of Sholingur
British East India Company and allies (company army/confederacy); Kingdom of Mysore (kingdom)
Hyder Ali; Eyre Coote; Hyder Ali
Another reverse for Mysore in the Carnatic without ending the war.
colonial archival record, government/institutional historical account, scholarly reconstruction. Institutional chronology explicitly records Mysore's loss at Sholinghur.
Town identification is secure; exact battlefield needs cartographic research.
modern town and temple landscape. Modern town and sacred hill are not automatically the battlefield.
Company forces attacked Panchalankurichi in 1799; the fort fell after resistance.
Participants: Panchalankurichi Palaiyam resistance and British East India Company forces
Outcome: Company capture and destruction of the fort; Kattabomman escaped before later capture.
Why it mattered: A central, archaeologically anchored site in southern resistance history.
Also known as: First siege of Panchalankurichi
Panchalankurichi Palaiyam resistance (resistance force/local ruler); British East India Company forces (company army)
Veerapandiya Kattabomman; Veerapandiya Kattabomman; John Bannerman
Escalated repression and resistance across the southern palaiyams.
colonial archival record, archaeology, government archaeological account. Tamil Nadu Archaeology records the site, 1799 campaign and named Company burials.
Protected site and associated military tombs secure the place identification.
reconstructed fort/memorial landscape and protected tombs. Protected/memorial site; public access and interpretation require current official checks later.
Resistance forces reoccupied/rebuilt Panchalankurichi and fought Company assaults in 1801.
Participants: Panchalankurichi and allied resistance forces and British East India Company forces
Outcome: Company capture after renewed fighting.
Why it mattered: Distinct from the 1799 siege and tied to a wider 1801 campaign.
Also known as: Second siege of Panchalankurichi
Panchalankurichi and allied resistance forces (resistance force); British East India Company forces (company army)
Oomathurai
Resistance continued toward Sivaganga and Kalaiyar Kovil before suppression.
colonial archival record, archaeology, government archaeological account. Tamil Nadu Archaeology records tomb dates in March and May 1801 and identifies soldiers killed in fighting with Oomathurai.
Dated burials and protected site provide strong location evidence.
reconstructed fort/memorial landscape and protected tombs. Protected/memorial site; no current access promise.
Sepoys seized much of Vellore Fort before a Company relief force suppressed the uprising.
Participants: Rebelling sepoys of the Madras Army and British East India Company garrison and relief force
Outcome: Uprising suppressed with heavy loss of life.
Why it mattered: A precisely located, archive-rich early nineteenth-century uprising.
Also known as: Vellore Mutiny; Vellore Revolt
Rebelling sepoys of the Madras Army (resistance force/company soldiers); British East India Company garrison and relief force (company army)
Members of Tipu Sultan's family held at Vellore
Regulations and Madras administration were reviewed; the event became a major precursor in histories of military resistance.
colonial archival record, government/institutional historical account, scholarly reconstruction. Contemporary inquiries and later scholarship support the date, site and broad causes while interpretations vary.
Exact fort location is certain.
fort, museum/heritage and active sacred/civic spaces. Vellore Fort is a living multi-use heritage complex; verify access and respect religious sites.
Method
Exact dates are used only where records support them. “Approximate” preserves a range or scholarly estimate rather than manufacturing a single year.
A high-confidence modern town does not automatically establish an exact battlefield. The place bridge identifies the level the reviewed evidence can sustain.
Inscriptions, archaeology, chronicles, archives, institutional histories, literary traditions and scholarly reconstruction answer different questions and have different limits.
The reviewed evidence contains no verified coordinates for these 18 records, so this release does not add event markers to Maps. That restraint prevents modern towns from being presented as exact battlefields. Read the site-wide Source Policy.
Responsible visiting
Historical conflict sites may now be active towns, religious places, protected monuments, archaeological areas or local landscapes. Respect access restrictions, religious practice, archaeological protections, local communities and monument rules. A place named in a record is not a promise of public access or visible remains.
Coverage
This timeline is selective, evidence-led and will expand as additional events and locations are verified. It is not a list of every war in Tamil Nadu. The structured registry can accept later verified additions without changing the page architecture.