SOURCE REVIEW · 2026-09-28

Tipu Sultan.
Follow the evidence.

Named damage, surviving shrines, and the accounts behind each attribution.

This review adds 11 dossiers, including reported destruction by Tipu’s forces, looting, a disputed attribution and damage attributed to a different army. They are not 11 verified demolitions by Tipu.

Named temple damage attributed to Tipu Sultan, the sources behind those claims, and conflicting attribution. This is a source audit, not a complete inventory of his campaigns. Exact dates remain unresolved where the sources do not provide them. Patronage and damage are assessed as separate events.

Mapped cases

Rajarajeshwara Temple, Taliparamba

Historical accounts attribute the loss of gateway towers to Tipu’s forces; they do not establish demolition of the whole temple.

Attribution: Tipu Sultan’s forces

Open on the map ↗

Thrikkavu Durga Temple

Logan records an account of a broken image, plunder and use of the shrine as a powder magazine, followed by repairs.

Attribution: Tipu Sultan

Open on the map ↗

Ponmeri Shiva Temple

A nineteenth-century district notice attributes destruction to Tipu’s soldiers; the precise extent and year are unresolved.

Attribution: Tipu Sultan’s forces

Open on the map ↗

Thiruvangad Sree Ramaswamy Temple

Retrospective government accounts attribute partial damage to Tipu and describe later repairs.

Attribution: Tipu Sultan’s forces

Open on the map ↗

Guruvayur Sri Krishna Temple

Accounts describe damage to subsidiary shrines during Tipu’s campaign, while the main shrine survived; a separate 1970 fire caused major losses.

Attribution: Tipu Sultan’s forces · A responsible individual or organization has not been established.

Open on the map ↗

Historical Jain temple at Periyapatna

Buchanan reports destruction of a Jain temple used to store British army gunpowder.

Attribution: Tipu Sultan

Open on the map ↗

Perur Pateeswarar Temple

Buchanan reports the seizure of temple gold and jewels while worship and the building survived.

Attribution: Tipu Sultan

Open on the map ↗

Hemambika / Emoor Bhagavathy Temple

Buchanan describes a temple at Callay Colam that Tipu had pulled down, with its distinctive hand-shaped image surviving.

Attribution: Tipu Sultan

Open on the map ↗

Earlier temple at the Masjid-i-Ala site

Kirmani describes a temple’s purchase, removal of its image and demolition before construction of the mosque.

Attribution: Tipu Sultan

Open on the map ↗

Bhagandeshwara Temple, Bhagamandala

Moegling attributes damage to roof tiles to Viraraja’s cannon fire during the recapture from Mysorean forces.

Attribution: Viraraja’s forces

Open on the map ↗

Harihareshwara Temple, Harihar

A report-based attribution to Tipu is disputed; the source chain concerns damaged images, plunder and partial conversion, not a securely established total demolition.

Attribution: Tipu Sultan · attribution disputed

Open on the map ↗

What the sources change

Partial destruction needs a precise description

Taliparamba’s gopurams and Thiruvangad’s wall are named damaged components. The sources do not establish complete demolition of either complex.

Rajarajeshwara Temple, Taliparamba ↗Thiruvangad Sree Ramaswamy Temple ↗

A Jain site and a looting case from an earlier survey

Buchanan reports a Jain temple explosion at Periyapatna and looting at Perur. The former remains a town-level location; the latter must not be relabelled as a razed temple.

Historical Jain temple at Periyapatna ↗Perur Pateeswarar Temple ↗

A citation points to the wrong temple

The Bhagamandala article cites Moegling p. 98 for a Tipu destruction, but that page concerns Padinalkanadu and Payavur. The mapped Bhagamandala episode follows p. 102, which identifies Viraraja’s cannon fire.

Bhagandeshwara Temple, Bhagamandala ↗

Demolition and the terms of acquisition are separate claims

Kirmani’s court account describes consent and removal of a bull image before demolition for Masjid-i-Ala. Consent and the image’s identity remain attributed to that account.

Earlier temple at the Masjid-i-Ala site ↗

A later scholarly citation still needs its original document

The Harihar chain runs through a quoted village-accountant document and the Mysore survey. A competing temple booklet may describe another episode; the atlas retains disputed attribution.

Harihareshwara Temple, Harihar ↗

An aggregate is not an inventory

The “8,000 temples” claim is not a verified total in this edition. No unnamed total is expanded into individual markers. The atlas and this targeted review remain incomplete.

14 source trails

A source can be old without being an eyewitness account. An official publication may repeat an earlier gazetteer. These notes distinguish text inspected directly from works known only through someone else’s citation.

Logan, Malabar, volume II (1887) ↗

Where it comes from: Colonial district handbook compiled by Logan with contributing local officers, about a century after the campaigns.
What was read: Original-edition OCR passages read: Appendix XXI, Taliparamba, Ponmeri and Trikkavu entries.
What it supports: Explicitly supports named damage accounts. Taliparamba concerns gateway towers; Trikkavu uses reported-account wording. Two Ponmeri notices in the same volume are not two independent witnesses.
Earlier sources and dependencies: The notices do not identify a contemporary document for each attack. Later websites repeat them.
Next evidence to check: Compare scanned pages with OCR, identify the taluk contributors and inspect any surviving local temple records. The date of publication is not the date of destruction.

Buchanan, Journey from Madras, volume II (1807) ↗

Where it comes from: Travel survey commissioned by the East India Company; records a journey in 1800 after Tipu’s defeat.
What was read: Original OCR passages read: pp. 96 (Periyapatna), 251 (Perur), 332 (Anamalai), 352 (Callay Colam).
What it supports: A substantially earlier source than modern compilations. Describes a Jain temple explosion, Perur looting, five unnamed temples dismantled for fort repairs, and a Bhagavathy temple rebuilt around a surviving image. He saw the places later, not the attacks.
Earlier sources and dependencies: Accounts from people and officials encountered during the survey; witnesses are not individually named in these passages. Colonial patronage and the author’s hostile judgments need to remain visible.
Next evidence to check: Locate the historical Periyapatna Jain building and the five Anamalai temples. Do not convert the five unnamed buildings into five invented points. The report of a general destruction order on p. 251 is immediately qualified as unenforced.

Kirmani, History of the Reign of Tipu Sultan; Miles translation (1864) ↗

Where it comes from: Near-contemporary Persian court history transmitted here through a later English translation.
What was read: Printed pp. 140–142 read in original translation OCR.
What it supports: Describes purchase of a temple, the worshippers removing its bull image, and demolition for Musjid-i-Ala. Consent is a claim made by the court narrative, not independently established. Its prophecy story is not verification of the event.
Earlier sources and dependencies: Persian manuscript → William Miles translation → modern retellings. A modern Hanuman identification does not match the bull-image description in this passage.
Next evidence to check: Collate the Persian text, translation and archaeological record. Do not silently relabel a narrated purchase as forcible seizure or assign the mosque’s completion date to the demolition.

Mysore Archaeological Survey, collected 1910–1912 reports ↗

Where it comes from: Mysore state archaeological department, led by R. Narasimhachar; combines inscriptions, observations and historical statements.
What was read: Varahasvami paragraph read in the collected-volume OCR. The particular Harihar p. 22 passage has not been located in this file.
What it supports: Attributes demolition of the Seringapatam Varahasvami temple to Tippu and dates installation of its image at Mysore to 1809. That restoration year is not a demolition date.
Earlier sources and dependencies: The 1912 Harihar passage is quoted by Olikara as reporting an old record shown by village accountant Srinivasa Sitarama Kulkarni. That quoted record is a different level of evidence from an observed eighteenth-century attack.
Next evidence to check: Locate the exact annual-report pages and the underlying Harihar manuscript; identify the historical Varahasvami site separately from the surviving shrine in Mysore.

Narasingha P. Sil, SAGE Open (2013) ↗

Where it comes from: Scholarly interpretive article, not a new archaeological survey.
What was read: Article and bibliography read.
What it supports: Names Harihar, Varahasvami and Odakaraya. Its brief “destroyed” formulation requires checking against accounts that distinguish broken images, plunder and partial conversion.
Earlier sources and dependencies: Sil cites Kate Brittlebank (1997), pp. 125–126, and Logan. Brittlebank’s book pages were not directly read in this review; the Monash thesis catalogue supplied no public file.
Next evidence to check: Consult Brittlebank’s actual text and footnotes. A cited book, a scholarly article citing it and websites repeating the article are not three independent original witnesses.

Nidhin Olikara, The Seringapatam Times (2014) ↗

Where it comes from: Research blog arguing against the Tipu attribution; reports visits to an archive and the temple.
What was read: Full article read; quoted report and temple booklet not independently inspected.
What it supports: Useful for identifying the manuscript-to-survey-to-scholarship chain and a competing temple account. Its forceful conclusion goes beyond what omission in a later booklet alone can establish.
Earlier sources and dependencies: Brittlebank → 1912 Mysore report → accountant’s old document. Counter-account: Harihara Kshetra Mahathme booklet, translated in the blog, assigning an attack to Bijapur forces.
Next evidence to check: Determine whether the accounts describe different episodes. Preserve disputed attribution until the documents and chronology can be compared.

Hermann Moegling, Coorg Memoirs (1855) ↗

Where it comes from: Missionary-era retrospective history with a sympathetic account of the Coorg ruler.
What was read: Original OCR, printed pp. 97–103, read.
What it supports: Page 98 describes burning at Padinalkanadu and Payavur, not Bhagamandala. Page 102 reports damage to Bhagamandala roof tiles from Viraraja’s cannon fire and their replacement.
Earlier sources and dependencies: Wikipedia’s Bhagamandala article cites p. 98 for destruction by Tipu. The inspected passage does not support that named-site claim.
Next evidence to check: Identify the Padinalkanadu and Payavur temples. Find separate evidence, if any, for damage to Bhagamandala under Tipu; the citation mismatch alone does not prove no other damage occurred.

Cannanore District Census Handbook, 1981 series ↗

Where it comes from: Official retrospective district description.
What was read: Full PDF text retrieved with Firecrawl; Taliparamba and Tellicherry paragraphs read.
What it supports: Specifies partial blasting of Taliparamba gopurams and damage to a Thiruvangad wall, with a repair attributed to Baber in 1815. Neither supplies a precise attack date.
Earlier sources and dependencies: Underlying historical sources are not individually identified in these paragraphs. Possible dependence on older gazetteers is unresolved.
Next evidence to check: Compare the handbook and gazetteer wording, then trace the repair record. Official publication does not automatically make it independent confirmation.

Kerala Tourism: Thiruvangad ↗

Where it comes from: Government heritage description.
What was read: Page read directly.
What it supports: Describes partial damage by Tipu’s forces but uses chronologically imprecise mid-eighteenth-century wording. The atlas does not turn it into an exact year.
Earlier sources and dependencies: No archival citation on the page; wording may share a common source with later reference accounts.
Next evidence to check: Resolve campaign dating against contemporary military and temple records.

Heaven on Earth: Guruvayur page extract hosted by Sahapedia ↗

Where it comes from: Published heritage-history extract; authorship of the supplied page has not been established.
What was read: Supplied PDF extract read; complete book and footnote 27 unavailable in the extract.
What it supports: Describes plunder, subsidiary-shrine destruction and fire; also recounts a miraculous voice and rain. Preserves the distinction between damage within a surviving complex and total destruction.
Earlier sources and dependencies: Footnote 27 is the next source to inspect. Similar wording on several travel and reference pages is not evidence of independent witnesses.
Next evidence to check: Obtain the book’s title/credits and note 27. The 1789 campaign date in the dossier is separately sourced to the reference chronology.

C. Achyuta Menon, Cochin State Manual (1911) ↗

Where it comes from: Cochin state historical-administrative compilation.
What was read: Original OCR passages on lost temple records, an island in the Alwaye area and the Travancore lines read.
What it supports: Describes regional temple losses but does not individually identify each affected building. These statements remain locality/group leads.
Earlier sources and dependencies: A source named in the Ravi Varma bibliography; it is distinct from K. P. Padmanabha Menon’s History of Cochin.
Next evidence to check: Resolve the island/place heading and named temples. Do not assign every temple in a five- or six-mile radius an event merely from the regional statement.

B. Lewis Rice, Mysore gazetteer editions ↗

Where it comes from: Colonial administrative gazetteers; online claims commonly cite the title without a volume/page.
What was read: OCR searched in 1877 volume I and 1897 volumes I and II; selected surrounding passages inspected. Not read cover to cover.
What it supports: The frequently repeated “8,000 temples” figure was not verified in the editions checked. OCR and edition coverage limit this negative result; it is not a proof that no such statement appears anywhere.
Earlier sources and dependencies: Ravi Varma’s anthology chapter and Sandeep Balakrishna’s article attribute an aggregate to Rice; the latter also invokes R. D. Palsokar without an exact locator for this number.
Next evidence to check: Require an edition, page and the original underlying statement. An aggregate, even if located, would still not supply 8,000 individually identified temples.

Ravi Varma anthology chapter and later web compilations ↗

Where it comes from: An advocacy anthology written in the controversy over Tipu’s public portrayal; modern polemical articles reuse many of its examples.
What was read: Named-site list and bibliography read; Prekshaa and the CSIS India republication compared.
What it supports: Valuable discovery lists, but they mix demolition, looting, relocation, temple tradition and broad regional claims. Repeated names and variant spellings need deduplication. Their broad judgments about religious communities are not adopted by the atlas.
Earlier sources and dependencies: Varma names Logan, Buchanan, Rice, regional histories and temple records. Prekshaa invokes P. C. N. Raja and related accounts; its text reappears on CSIS India. Dependency is apparent for shared passages, while the complete copying history is not established.
Next evidence to check: Resolve each named claim to an exact older passage. Vadakkunnathan appears in a destruction list while the reference article describes it as spared, illustrating why wholesale list import is unsafe.

Sringeri institutional history ↗

Where it comes from: History published by the affected religious institution.
What was read: Institutional biography consulted in the earlier expansion; original correspondence not independently inspected.
What it supports: Attributes the 1791 plunder to Maratha forces and describes Tipu’s restoration aid. This is a separate event, not evidence that other attributed attacks did or did not occur.
Earlier sources and dependencies: The biography discusses correspondence between Tipu and the Sringeri guru. The physical letters and their original language remain a further source layer.
Next evidence to check: Inspect the correspondence editions and images. Keep patronage and damage as separate, site-specific claims.

43 follow-up records

These are named compilation claims and leads from older books, with variant names grouped. They are not additional verified destroyed temples. Group-level reports remain single leads until the individual buildings can be identified.

Triprangot / Thriprangatu — Tipu attribution

Triprangode. Named in a later compilation; exact event, date, affected fabric and source chain require verification. Variant names are grouped; listing does not establish destruction.

Status: needs underlying source check
Source trail: Tipu source review: named claim in anthology / compilation

Tipu Sultan.Follow the evidence.

Mapped cases

What the sources change

Partial destruction needs a precise description

A Jain site and a looting case from an earlier survey

A citation points to the wrong temple

Demolition and the terms of acquisition are separate claims

A later scholarly citation still needs its original document

An aggregate is not an inventory

14 source trails

43 follow-up records

Bibliographies behind the modern accounts

Tipu Sultan.
Follow the evidence.