The reign of Evil-merodach

• Evil-merodach

• Start — Jeremiah 52:31. The year Evil-merodach's reign began is the year Jehoiachin's exile began (3365) + 37 years = 3402
• End — no reference given. The year Evil-merodach's reign ended is the year his reign began (3402) + the length of his reign (2 years) = 3404

START:[Shulman date p143] [Ussher date p110] END:*EXTRA-BIBLICAL SOURCES: - Berossus, a Hellenistic-era Babylonian priest and historian, is cited in later works (e.g., by Josephus and Eusebius) stating that Evil-Merodach reigned for two years before being assassinated by his brother-in-law, Neriglissar. His account, preserved in fragments, describes Evil-Merodach’s rule as "lawless and outrageous," leading to his overthrow after a short reign. This aligns with the two-year timeframe. - Abydenus, another ancient historian, is referenced in the McClintock and Strong Biblical Cyclopedia as assigning Evil-Merodach a reign of two years. His works, though surviving only in fragments, corroborate Berossus’ account of the brief rule ending with Neriglissar’s usurpation. - The Canon of Ptolemy, a chronological list of kings, records Evil-Merodach (under the name Ilvoradam or similar) as reigning for two years, from 562 to 560 BCE. This astronomical and historical document is considered a reliable source for Babylonian chronology. - Approximately 30 cuneiform contract tablets dated to Evil-Merodach’s reign have been discovered, covering a period of about two years and five months (562–560 BCE). These tablets, used for economic transactions, provide direct evidence of his rule’s duration, as they cease after August 560 BCE, when Neriglissar’s documents appear. - The Uruk King List, a cuneiform document, records the reigns of Babylonian kings. While it does not provide detailed narratives, it confirms Evil-Merodach’s reign as brief, consistent with the two-year period noted in other sources. [Shulman date p143] [Ussher date p111]

Years are anno hominis — counted from Creation as year 1 — which is the frame the source computes in. The arithmetic behind each boundary is given above rather than assumed.