The kingdom of Sumer and Akkad, reconstituted by an officer sent north for grain when Ur fell, holding the old title two centuries before a rival it had once beaten ended it - by whose hand, no source says.
Still contestedKing, A History of Sumer and Akkad (1910)
Languages of administration
Akkadian
Sumerian
Writing system: Cuneiform
Core region
Sumer and Akkad, southern Mesopotamia
How it was governed
2 of 4 coded
Army raised byHow the fighting force was recruited, not how it fought.
No cited figure
Revenue fromWhat the state lived on. The values are unranked: the field cannot express which mattered most.
No cited figure
Succession byThe rule in force, not the outcome. A rule repeatedly violated is still the rule.
primogenitureThe eldest son
King, A History of Sumer and Akkad (1910)
Right to rule fromThe ground publicly asserted — on coins, in the khutba, in titles.
descentDescent from a house or lineage, publicly invoked
divine sanctionA mandate from above — heaven, or a claim to be mahdi or imam
King, A History of Sumer and Akkad (1910)
Each line is drawn from a source that addresses the question directly. A line reads No cited figure where no source consulted does — never because the answer seemed obvious.
Turning points
4 hinges
2004 BC1778 BC
2004 BC
Ishbi-Erra's refoundationRevolt
A trusted subordinate, stranded away from his own capital by a catastrophe he had not caused and could no longer reverse, chose to build rather than return, expelling the invaders who now held his former master's city and claiming the old royal style for a settlement of his own founding instead.
King, A History of Sumer and Akkad (1910)
1910 BC
Gungunum's secession at LarsaSuccession crisis
A city this dynasty had long controlled through appointments at neighboring Ur stopped waiting for permission and began issuing its own royal inscriptions, asserting the same claim to Sumer and Akkad the ruling family had held unchallenged for ninety-four years.
King, A History of Sumer and Akkad (1910)
1908 BC
The laws of Libit-IshtarReformContested
A prologue naming the gods' mandate, a body of conditional provisions on slavery, inheritance, land and hire, and an epilogue of blessings and curses — the same three-part structure Ur-Nammu's collection had used two centuries earlier and Hammurabi's would use a century and a half later. No court record ever cites it as the authority for a verdict, but scribal schools copied it for centuries after the dynasty that produced it had ended, which is where its actual influence lies.
Roth, Writings from the Ancient World 6 (1997)
1780 BC
The dynasty ends without a recorded causeCatastropheContested
A line that had held the old royal title of Sumer and Akkad for two and a quarter centuries disappears from the king list after Damik-ilishu, and nothing in the surviving record states how or by whom. The captures later date-formulas credit to Larsa and to Babylon both turn out, once the chronology is checked, to belong to a struggle fought after Isin's own kingship had already ended by some other, unrecorded means.
King, A History of Sumer and Akkad (1910)
Chapters
7 in order · about 12 minutes
An officer sent for grain
formationDrafted from King, A History of Sumer and Akkad (1910)
The kingdom of Sumer and Akkad did not die with the fall of Ur; the
throne simply moved. Ibbi-Sin, Ur's last king, had sent one of his own
officers, Ishbi-Erra, north to buy grain during a famine that was
already loosening his grip on the kingdom. While Ishbi-Erra was away
from the capital, an Elamite army overran Ur itself and carried Ibbi-Sin
off in captivity - and rather than return to a throne that no longer
existed, Ishbi-Erra used the resources already in his hands to found a
kingdom of his own at Isin, drove the Elamite garrison back out of Ur,
and took up the old royal title, King of Sumer and Akkad, that his
former master had just lost.
A student scribe's copy of four letters from the reign of Ibbi-Sin, the correspondence in which Ishbi-Erra appears, made in the schools of the following centuries.
Oriental Institute Museum, University of Chicago · King, A History of Sumer and Akkad (1910) · Daderot · CC0
A dynasty rather than an accident
What might have been a single opportunist's lucky escape became,
instead, a durable royal house. Ishbi-Erra ruled for thirty-two years
and firmly established his own family on the throne, and four of his
direct descendants succeeded him in turn without incident, their
combined reigns spanning ninety-four years. Each claimed, and by the
evidence of building inscriptions at Nippur, Ur and Eridu actually
exercised, real authority over the old Sumerian heartland - not a
government in exile, but the kingdom of Sumer and Akkad genuinely
continuing under a new address.
A famine that ended one kingdom and began another
The irony the sources preserve is that Ishbi-Erra's entire rise began
with a supply mission, not a battle - he was never recorded fighting
his way to the throne of Ur, only failing to return to a city that had
already fallen behind him. What he built afterward, a hundred miles
away at Isin, would outlast the catastrophe that made it possible by
more than two centuries.
A daughter sent to Anshan
expansionDrafted from King, A History of Sumer and Akkad (1910)
Between Ishbi-Erra's own reign and his great-grandson Ishme-Dagan's, two
kings held the throne whose combined years the sources credit without
dwelling on — Shu-Ilishu and, at greater length, Iddin-Dagan, whose own
year-names supply most of what can be said about either reign.
A marriage recorded because it was worth dating by
Mesopotamian scribes named each year after its most significant event
rather than counting them in sequence, and one of the events chosen to
name a year of Iddin-Dagan's reign was the marriage of his own daughter to
the ruler of Anshan, in the Elamite highlands east of Sumer. A scribe does
not build a whole year's official dating formula around a domestic event
of no consequence; a marriage judged worth naming a year after is a
marriage understood, at the Isin court itself, as a diplomatic achievement.
The alliance follows a pattern this region's kings used repeatedly and
would go on using for the next fifteen hundred years: binding a
neighbouring power that could otherwise threaten a frontier by attaching it
to the ruling family through a daughter's marriage rather than through a
garrison. Elam had supplied the army that ended Ur's own dynasty a
generation earlier; a king of Isin whose own founder had built his kingdom
on Ur's collapse had every reason to want the same power tied to his own
house by something more durable than a treaty a change of ruler could
undo.
The rite the family kept
Whatever else Iddin-Dagan's reign accomplished, one further year-name
credits him with celebrating the sacred marriage rite in which the king
took the role of the god Dumuzi to the goddess Inanna's own high priestess,
renewing the land's fertility and the dynasty's own favour in the same
ceremony. It is the earliest such celebration this dynasty's own record
credits to a named king, and it did not stop with him: Ishme-Dagan and his
son Libit-Ishtar, a generation and two generations later, are both
independently attested continuing the same rite.
A hymn to Iddin-Dagan of Isin, the composition that describes the sacred marriage rite.
Musée du Louvre, Paris · King, A History of Sumer and Akkad (1910) · Marie-Lan Nguyen · Public domain
A practice three successive kings maintained across three reigns is not an
individual ruler's private devotion. It is a piece of royal ceremony the
Isin dynasty had adopted as part of what a king of Isin was expected to do,
and Iddin-Dagan's own year-name is the earliest point at which the record
catches the family already doing it.
Titles a family earned
peakDrafted from King, A History of Sumer and Akkad (1910)
Ishme-Dagan, the fourth king of Ishbi-Erra's line, ruled the fullest
version of the kingdom his great-grandfather had improvised. His own
inscriptions claim, in addition to King of Isin and King of Sumer and
Akkad, the title Lord of Erech, and record favor shown to the temples
of Nippur, Ur and Eridu in turn - a claim to authority over every major
Sumerian religious center, not just the new capital. Bricks bearing
his name and titles, recovered at Nippur in quantity, show building
work substantial enough to back up the claim rather than merely assert
it.
One of the bricks stamped with Ishme-Dagan's own name and titles, found at Ur — the building record that backs up what his inscriptions claim rather than standing in for it.
British Museum, London · King, A History of Sumer and Akkad (1910) · Photograph: Osama Shukir Muhammed Amin · CC BY-SA 4.0
A king who married a goddess
Ishme-Dagan went further than his predecessors in another direction as
well, styling himself the "beloved spouse" of Ninni, the great goddess
of Erech - a claim to divine consort status the kings of Isin had
inherited as a practice from the earlier Dynasty of Ur, and one
Ishme-Dagan's own son Libit-Ishtar continued after him. Divine rank
and real administrative reach reinforced each other: a king secure
enough in his own legitimacy to claim marriage to a goddess was also,
in this case, a king whose officials' presence is independently
attested at every major city of the south.
A peak that was already, quietly, an ending
Ishme-Dagan reigned twenty years, closing out the ninety-four years his
own great-grandfather's direct line had held the throne without
interruption. His son Libit-Ishtar succeeded him and reigned eleven
years more - but it was during or immediately after Libit-Ishtar's own
reign that a local governor at Larsa, a city the dynasty had controlled
through its own priestly appointments at neighboring Ur, broke away and
declared himself king in his own right. The most fully titled reign in
the dynasty's history and the moment its slow fragmentation began
turn out, in the sources, to sit right next to each other.
The code Lipit-Ishtar left
asideDrafted from Roth, Writings from the Ancient World 6 (1997)
Libit-Ishtar, Ishme-Dagan's son and successor, is remembered for one thing
above everything else his eleven-year reign accomplished: a collection of
laws issued in his own name, roughly a century and a half before Hammurabi
issued the collection that would eventually eclipse it in fame.
What the code actually is
A votive cone carrying Lipit-Ishtar's own inscription — the ordinary genre of royal building record his name survives on most often, distinct from the law collection this chapter is actually about.
Metropolitan Museum of Art, New York · Roth, Writings from the Ancient World 6 (1997) · Metropolitan Museum of Art · CC0
The Lipit-Ishtar code survives in the same three-part structure later
Mesopotamian law collections would keep: a prologue in which the king
explains why the gods chose him to establish justice, a body of specific
conditional provisions — if a man does this, then this is the
consequence — covering slavery, inheritance, land tenure, marriage and
the hire of boats and oxen, and an epilogue invoking blessings on whoever
respects the king's work and curses on whoever defaces it. Roth's edition
prints it beside the law collection of Ur-Nammu, two centuries older
still, and beside Hammurabi's, a century and a half younger, and the family
resemblance across all three is immediate: this is a genre with an
established form by the time Libit-Ishtar's scribes sat down to draft it,
not an innovation of his own devising.
What it was actually for
Like the other collections in Roth's volume, the Lipit-Ishtar code was
almost certainly not a functioning law book in the sense a modern reader
would recognise — no surviving Mesopotamian court record cites it as the
authority for a specific verdict, in this period or any other. What it did,
and did successfully, was declare in permanent, public form that the king
had set the kingdom's affairs in order: a royal claim to justice made
concrete in the same genre a predecessor and a successor both used to make
the identical claim.
Outliving the dynasty that produced it
The code's actual influence shows up not in courtrooms but in schools.
Copies of the Lipit-Ishtar prologue and provisions continued to be made and
studied by scribal students for centuries after the Dynasty of Isin itself
had ceased to exist, alongside the law of Ur-Nammu and, eventually,
Hammurabi's own — the same three-stage transmission this region's legal
writing shows across a thousand years and multiple languages, in which
Libit-Ishtar's is neither the first entry nor the last, but a genuine link
in the middle of the chain.
A dynasty two-thirds of the way through its own existence, its throne about
to pass out of the founder's family entirely, produced a text that would
still be copied by students long after every other trace of the family had
gone.
A throne without a family
contractionDrafted from King, A History of Sumer and Akkad (1910)
After Libit-Ishtar, the throne of Isin passed out of Ishbi-Erra's own
family entirely. What followed is not one story but two running side by
side: a capital that kept its old titles and a kingdom that stopped being
able to guarantee who would hold them next.
The titles outlasted the line
Ur-Ninib, whose relationship to the preceding kings the record does not
state, took the throne after Libit-Ishtar and held it for twenty-eight
years; three of his own descendants followed him in turn, and between them
the new line held Isin for sixty-one years. They styled themselves with
the same full royal titulature — King of Isin, King of Sumer and Akkad —
that Ishbi-Erra's own descendants had claimed, and nothing in the record
suggests any of Isin's subjects treated the new family's kingship as less
legitimate for not descending from the founder. A title, once established,
turned out not to require the specific bloodline that had first claimed
it.
Larsa stops waiting
It was during this same period that the break at Larsa, already visible
under Libit-Ishtar, took permanent root. Gungunum, governing the city on
Isin's own former authority, had stopped issuing his inscriptions in
Isin's name and begun asserting the old royal claim to Sumer and Akkad in
his own right.
His successors at Larsa spent the following decades steadily converting
that assertion into territory, taking cities and canal rights that had
once been unambiguously Isin's to tax, while Isin's own new ruling family
held its capital and its titles without, on the evidence available, doing
much to reverse Larsa's steady encroachment.
Five kings, thirty-six years, no family
Ur-Ninib's own line ended after sixty-one years, and what followed was
worse than a change of dynasty: thirty-six and a half years in which five
kings, unrelated to each other so far as the record shows, held the
throne of Isin in rapid and unexplained succession. No source states why
each reign ended when it did or how the next king came to the throne
after it; the pattern itself is the evidence, and what it is evidence of
is a kingdom that had stopped being able to produce, or at least to keep,
an heir capable of holding the position for long.
A foundation cone of Enlil-bani, one of the kings of the unsettled decades at Isin, recording a temple he built for the god Numushda at Kiritab.
Sulaymaniyah Museum · King, A History of Sumer and Akkad (1910) · Osama Shukir Muhammed Amin · CC BY-SA 4.0
A capital that still called itself the seat of Sumer and Akkad, ruled in
these decades by a rotating cast of kings with no evident claim on each
other, while a rival forty miles away steadily annexed the territory the
title was supposed to describe: that is the condition Sin-magir inherited
when stability finally returned, and what he and his son made of it is
where the dynasty's story actually ends.
An end no source can quite place
endDrafted from King, A History of Sumer and Akkad (1910)
Only in the dynasty's final generation, after the thirty-six and a half
years of rapid, unrelated kings described in the previous chapter, did the
throne of Isin settle again. Sin-magir and his son Damik-ilishu between
them held it for thirty-four comparatively stable years — the longest run
of orderly succession the dynasty had managed since Ishbi-Erra's own
direct line ended — and it was this final, quieter generation that closed
the dynasty out altogether.
A question the sources cannot settle
Exactly how the dynasty ended is one of the genuinely unresolved
questions in the record. Later date-formulas commemorate a capture of
the city of Isin - one crediting Rim-Sin, king of Larsa, another
crediting Sin-muballit, a king of Babylon and Hammurabi's own father -
and it has been tempting to read one or both of these captures as the
dynasty's actual end, under Damik-ilishu himself. But the chronology
does not hold up cleanly under scrutiny: Rim-Sin's own reign can be
shown to extend well into the time of Hammurabi's son Samsu-iluna, far
too late for him to have also captured Isin in Damik-ilishu's own
generation, and the balance of evidence instead points to these
recorded captures belonging to a later struggle for the same city
between Larsa and Babylon - one that changed hands three times in
less than eleven years - fought a generation or more after the
Dynasty of Isin itself had already ended by some other, unrecorded
means.
A kingdom that outlived its own dynasty's memory
What can be said with confidence is only the shape of the outcome: a
line that had held the old royal title of Sumer and Akkad for two and
a quarter centuries disappeared from the king list after Damik-ilishu,
and the city of Larsa - once merely one governorship within Isin's
own kingdom - inherited the contest for supremacy in the south that
Isin itself had won at the very start of the story, from a different
rival, under very different circumstances.
The list that ends with Isin
afterlifeDrafted from Michalowski, Journal of the American Oriental Society (1983)
The most consequential thing to survive the Dynasty of Isin was not a
building, a treaty or even the law code the previous chapters describe. It
was a list — and the list itself argues, in its own construction, for
exactly the legitimacy the dynasty that compiled it needed.
What the Sumerian King List actually does
A copy of the Sumerian King List — the document that turns Ishbi-Erra's improvised refoundation into the latest stop of an office passed down, city to city, since before the flood.
Ashmolean Museum, Oxford · Michalowski, Journal of the American Oriental Society (1983) · Photograph: M.atkinsonross · CC BY-SA 4.0
The Sumerian King List presents Mesopotamian kingship as a single object
that descended, unbroken, from a moment before the flood down through a
sequence of cities — Kish, then Uruk, then Ur, and on through further
cities and dynasties — each holding "kingship" as a kind of movable office
that passed from one city to the next whenever the gods judged the time
had come, never split, never held by two cities at once, always
legitimately somewhere. Michalowski's argument is that the document
surviving to the modern reader took the particular shape it has because it
was compiled, or substantially reworked, at the court of Isin itself.
That framing does specific work for whoever compiled it. A list built to
show kingship as a single, continuous, transferable office, arriving at
its own present moment, is a list built to answer one question: which city
holds it now. Composed or finalised under an Isin king, the list answers
that question in exactly the way the Isin court needed answered.
An improvised throne, made to look inevitable
The dynasty's own founding was nothing like the orderly succession the
King List's structure implies. Ishbi-Erra was a supply officer who chose
not to return to a fallen city and built a kingdom out of what he happened
to be holding when the opportunity presented itself — the ordinary shape
of a governor an empire can no longer remove, not the kind of founding a
king wants remembered as the reason he rules.
The King List does not remember it that way. Read as Michalowski reads it,
the list quietly converts Ishbi-Erra's improvisation into the latest
transfer of an office that had been passing legitimately from city to
city since before the flood — the same office Kish held, then Uruk, then
Ur, now simply residing, as it always eventually had to reside somewhere,
at Isin. A text that looks like disinterested chronology is doing the
specific political work of making an opportunist's holding look like
destiny.
What outlasted the argument
The list's political usefulness to Isin's own kings ended when Isin's own
kingship did. Its usefulness as a chronological framework did not: copies
and versions of the King List continued to be made in scribal schools for
centuries afterward, read by scribes who had no stake in whether Isin's
own claim to the office had ever been deserved, using a document built to
flatter one vanished dynasty's legitimacy as the basic timeline for
everything that had supposedly happened before it.
Ur III's own end was an Elamite sack with no recorded successor state; Ishbi-Erra, an officer stranded outside the fallen capital, took up the old title King of Sumer and Akkad at a new city of his own founding rather than conquering anyone's throne. The edge records a claim, not a conquest.
No source states who or what actually ended the Dynasty of Isin, or when; the disputed captures later date-formulas credit to Larsa and to Babylon both belong, on the balance of the evidence, to a struggle fought a generation or more after Isin's own last king. What is certain is only that Larsa, once a governorship within Isin's own kingdom, inherited the title King of Sumer and Akkad and the contest for the south that went with it.
The shaded band is this polity’s span; the dark part of each bar is the stretch the two shared.
Derived from cited spans, not from a separate source. Where both spans are ranges and they meet only on the widest reading of each, the pair is listed as possible rather than resolved to one answer. Unlinked entries are here for scale and are not written up.
Extent
The historical-basemaps snapshots are world maps at fixed years, and none of the ones falling inside this polity's lifetime names it among the polities it draws.
Rating
Four axes, all computed from cited numbers and never from editorial judgement. Percentiles are against every polity written up here — 419 of them — plus 49 more included for scale. Absolute figures. A missing axis is excluded from the total rather than counted as zero.
Reach
No cited figure
Longevity
224–226 years
51st to 52nd percentile — the sources disagree on the span, so the rank is a range too
Demographic weight
No cited figure
Influence
Three separate counts. This site never publishes a single influence number of its own; the sliders on the rankings view fuse them only in your view.
Descendant scripts
0
Religions carried
0
Successor claims
0
Weighted total
46th percentile
computed from 2 of 4 axes, renormalised across the axes that have figures. A polity with two documented axes is not penalised against one with four.