Forty-five years and four reigns about which almost nothing is known beyond how the dynasty began - a Brahmin minister murdering the king he had already been ruling through - and how it ended, killed by a southern power that has left no monument at Pataliputra to prove it was ever there.
internal usurpation27 BCSmith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)
How it was governed
1 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.
No cited figure
Right to rule fromThe ground publicly asserted — on coins, in the khutba, in titles.
conquest
The right of the sword, asserted as such
Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)
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
2 hinges
72 BCVasudeva Kanva's coupsuccession crisis
The Brahmin minister who had been running the Shunga state behind its last dissolute king had him murdered and took the throne for himself - the fourth ruling house of Magadha in a row to begin with a trusted subordinate turning on the man he served.
Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)
27 BCSusarman killed by the Andhra kingsuccession crisis
A power from outside the sequence of Magadhan usurpations entirely - already ruling wide territory across the Deccan before it ever touched Pataliputra - closed out a line no internal rival had managed to unseat on its own.
Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)
Chapters
3 in order
The minister who had already won
Drafted from Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)formation
By the time Vasudeva Kanva had the last Shunga king killed, the throne he
was taking had already, in every practical sense, been his for some time.
A pattern with a name
Smith reaches for a comparison from much later Indian history to describe
what the Shunga-Kanva transition actually was: the relationship of the
later Maratha rajas to their own Peshwas, nominal kings governed in
practice by hereditary chief ministers who eventually held all the real
power the royal title implied. The later Shunga kings, on this reading,
had already stopped being rulers in anything but name well before Devabhuti
died — Vasudeva simply removed the last formality standing between his
existing control of the state and the title that matched it.
What the coup actually changed
Very little, on the evidence available. The capital stayed at Pataliputra.
The territory Vasudeva inherited was whatever remained of the already
contracted Shunga holdings in Magadha and the middle Gangetic plain — no
new conquest accompanied the change of dynasty, because none was needed;
the state Vasudeva took over was one he had already been administering.
What changed was a name on a throne that had, for some years before that,
belonged to him in every respect except the formal one.
The silence that follows
That is close to everything that can be said about how the dynasty began.
No inscription of Vasudeva's own reign survives to describe his own view
of the transition, no coinage can be attributed to him with confidence, and
the sources that preserve the story of the coup itself — the Puranas, and
Bana's drama composed centuries later at an entirely different court — have
nothing further to say about what the new king actually did with the power
he had just formally claimed.
A name on a coin
Drafted from Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)aside
Nobody knows who actually killed Susarman, the last Kanva king, beyond the
Puranic statement that it was a king of the Andhra dynasty — and even that
answer opens more questions than it closes.
The wrong king, ruled out
The Puranas treat the Andhra dynasty as following directly on from the
Kanvas, and on that basis identify Susarman's killer with Simuka, the
Andhra line's own founder. Smith rejects the identification outright: the
independent Andhra dynasty, ruling across the Deccan tableland from coast
to coast, had already existed since roughly 220 BC — more than a century
and a half before the Kanvas fell in 27 BC. Whoever killed Susarman cannot
possibly have been the Andhra dynasty's own founder, however neatly the
Puranic sequence would have it.
What a coin might settle
The best candidate available rests on numismatic evidence rather than any
narrative source: coins of northern type carrying the legend Sata, which
may preserve the name of the actual king responsible. Smith had earlier
proposed treating the Kanva and early Andhra dynasties as partly
contemporary rather than strictly sequential — a theory he explicitly
abandons by the time he writes this account, on the strength of both the
Puranas' and Bana's independent agreement that Devabhuti, the last Shunga,
was the one Vasudeva Kanva killed, which fixes the sequence more firmly
than the alternative allowed for.
An empire with no monument at the scene of its own conquest
No coin or inscription directly ties any Andhra king to Pataliputra itself.
What can be said is only that Andhra coinage from first to last shares
affinities with northern Indian mintages — a pattern that makes sense if
the dynasty held Magadha as a dependency for some period, but proves
nothing about the manner of conquest, its extent, or how long the arrangement
actually lasted. A dynasty that killed the last king to rule from
Pataliputra as a paramount power has left less physical trace of the act
than either of the two dynasties it displaced.
Four reigns
Drafted from Smith, The Early History of India, from 600 B.C. to the Muhammadan Conquest (1904)end
Vasudeva Kanva was succeeded by three of his own descendants. Between the
four of them, the dynasty held the throne for forty-five years — and of
those four reigns, nothing whatever is recorded beyond the bare fact of
succession.
What the silence implies
Smith reads the brevity of the reigns, taken together with the total
absence of any other detail, as its own kind of evidence: a dynasty this
poorly documented, following two predecessors whose ends were both violent
successions by trusted subordinates, most likely continued the pattern
rather than breaking it. Nothing survives to confirm that any of the four
Kanva kings died peacefully, and nothing survives to prove otherwise
either. The silence is total in both directions.
The last of them
The fourth king, Susarman, was killed in 27 BC by an Andhra ruler from the
Deccan, ending the shortest-lived and least documented of the four
dynasties to hold Magadha's throne in succession — Nanda, Maurya, Shunga,
Kanva — across the three centuries since Mahapadma Nanda first took it by
force from the Shishunagas.
What forty-five years of silence actually means
It does not mean nothing happened at Pataliputra between 72 and 27 BC. It
means that whatever happened left no inscription any later scholar has
found, no coinage any numismatist can attribute with confidence, and no
story any chronicler thought worth preserving beyond the two facts that
bracket the whole dynasty: how it began, and how it ended. Between a
minister's murder of his own king and a southern conqueror's murder of his
successor's great-grandson, forty-five years of Magadhan history have
simply vanished — not disputed, not contradicted by rival accounts, just
absent.
Vasudeva Kanva, the Brahmin minister already running the state behind its last dissolute king, had him murdered and took the throne himself - the fourth ruling house of Magadha in a row to begin with a trusted subordinate turning on the man he served.
A king of the Andhra dynasty, already ruling wide territory across the Deccan, killed Susarman and — on the evidence of coins of northern type bearing the Andhra name Sata found alongside Kanva-era material, rather than on any inscription found at Pataliputra itself — probably held Magadha as a dependency for some period afterward.
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 — 280 of them — plus 50 more included for scale. Absolute figures. A missing axis is excluded from the total rather than counted as zero.
Reach
No cited figure
Longevity
45 years
9th percentile
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
No cited figure
Religions carried
No cited figure
Successor claims
No cited figure
Weighted total
9th percentile
computed from 1 of 4 axes, renormalised across the axes that have figures. A polity with two documented axes is not penalised against one with four.