Amangkurat III of Mataram
ruler (susuhunan) of Mataram, 1703-1704
Amangkurat III (Amangkurat Mas; died in Dutch Ceylon (now Sri Lanka), 1734) was a short-lived susuhunan (ruler) of the Sultanate of Mataram, who reigned 1703–1705.
When his father Amangkurat II of Mataram died, he soon lost his half-uncle Prince Puger in the First Javanese War of Succession, which lasted for five years until the Dutch managed to install Prince Puger as Pakubuwono I. Amangkurat was deposed, but not caught until 1707. He was subsequently exiled to Ceylon, where he died some three decades after his ouster from power.
Origin
Born as Raden Mas Sutikna, according to the Babad Tanah Jawi, he was the only child of Amangkurat II, as his mother had used magic on another of Amangkurat II's wives to make them unable to conceive of child. Sutikna was also nicknamed Pangeran Kencet (Prince Heel), due to the deformity in his heel.
It is said that Sutikna was bad-tempered, temperamental, and a jealous man, especially if he knew there was another more handsome man. When acting as adipati anom (crown prince), he married his cousin, Raden Ayu Lembah, daughter of Prince Puger (future Pakubuwono I). Nevertheless, he divorced his wife due to her infidelity with Raden Sukra, son of Patih Sindureja. Raden Sukra was then murdered by Sutikna's bodyguard, and Prince Puger was forced to put capital punishment on her daughter, Lembah. Sutikna then married Raden Ayu Himpun, sister of Lembah.
Begin with the source’s own compact description: “Amangkurat III of Mataram” is ruler (susuhunan) of Mataram, 1703-1704. The dossier treats that line as a proposition to test through Amangkurat, Mataram and ruler, not as a finished interpretation.
Why this record matters
The phrase “ruler (susuhunan) of Mataram, 1703-1704” 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.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 10, 2026. The linked authority identifier is Q1866639. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1734, 1703, 1705 and 1707.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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
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 “Amangkurat III of Mataram”, its source revision and the description used here.
- Expand the search: follow Amangkurat III of Mataram primary sources, Amangkurat III of Mataram archive and Amangkurat 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 “Amangkurat III of Mataram”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Amangkurat III of Mataram” 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.