Battle of Sellasia
ancient battle between Macedon and Sparta

The Battle of Sellasia took place during the summer of 222 BC between Macedon and the Achaean League, led by Antigonus III Doson, and Sparta under the command of King Cleomenes III. The battle was fought at Sellasia, on the northern frontier of Laconia and ended in a Macedonian-Achaean victory.
In 229 BC, Cleomenes initiated hostilities against the Achaean League, the dominant power of the Peloponnese. In a series of campaigns, Cleomenes was successful in defeating the Achaeans, making Sparta the main regional power. This prompted the chief figure of the Achaean League, Aratus of Sicyon, to approach the King of Macedon, Antigonus III Doson, for military assistance. The Macedonians acquiesced on the terms that the Achaean surrender the formidable fortress of Acrocorinth to them. The Macedonians invaded the Peloponnese in 224 BC at the head of a Greek alliance and by 222 BC managed to hem Cleomenes in Laconia.
In the summer of 222 BC, the Macedonian and Achaean army advanced to Sellasia on the northern border of Laconia, where they encountered the awaiting army of Cleomenes. After a brief impasse, Antigonus launched an offensive against the Spartan positions on the fortified mountains of Olympus and Evas. While the Macedonian right flank routed the Spartan left wing on Evas, the battle on the other flank was heavily contested. After initially pushing back the Macedonian phalanx, the Spartans were driven from the field by the superior numbers of the Macedonians.
Begin with the source’s own compact description: “Battle of Sellasia” is ancient battle between Macedon and Sparta. The dossier treats that line as a proposition to test through Battle, Sellasia and ancient, not as a finished interpretation.
Why this record matters
The phrase “ancient battle between Macedon and Sparta” 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.
Chronology, provenance and viewpoint should be read together before a broad social or political interpretation is accepted. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q204343. None of the 0 selected statements returned an explicit reference.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Battle of Sellasia”, its source revision and the description used here.
- Expand the search: follow Battle of Sellasia primary sources, Battle of Sellasia archive and Battle 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 “Battle of Sellasia”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Battle of Sellasia” 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.