Battle of Pydna
battle of the Third Macedonian War

The Battle of Pydna took place in 168 BC between Rome and Macedon during the Third Macedonian War. The battle saw the further ascendancy of Rome in the Hellenistic world and the end of the Antigonid line of kings, whose power traced back to Alexander the Great's Diadochi Antigonus Monophthalmus. The battle is also considered to be a victory of the Roman legion's manipular system's flexibility over the Antigonid Macedonian phalanx's rigidity.
Prelude
The Third Macedonian War started in 171 BC, after a number of acts on the part of King Perseus of Macedon incited Rome to declare war. At first, the Romans won a number of small victories, largely due to Perseus' refusal to consolidate his armies. By the end of the year, the tide changed dramatically and Perseus had gained a success at the Battle of Callinicus and regained most of his losses, including the important religious city of Dion. Perseus then established himself in an unassailable position on the river Elpeus, in northeastern Greece.
The next year, command of the Roman expeditionary force passed to Lucius Aemilius Paullus, an experienced soldier who was one of the consuls for the year. To force Perseus from his position, Paullus sent a small force (8,200 foot and 120 horse) under the command of Publius Cornelius Scipio Nasica Corculum to the coast, a feint to convince Perseus that he was attempting a riverborne flanking maneuver. Instead, that night Scipio took his force south and over the mountains to the west of the Roman and Macedonian armies.
The public source identifies “Battle of Pydna” as battle of the Third Macedonian War. This brief keeps that definition visible, then builds a research path around Battle, Pydna and battle.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Battle of Pydna”, the useful work is to connect “battle of the Third Macedonian War” to the records capable of establishing context and consequence.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 15, 2026. The linked authority identifier is Q504739. The Library of Congress control number is sh85109269. Authority coordinates are 40.251, 22.474. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. 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 Pydna”, its source revision and the description used here.
- Expand the search: follow Battle of Pydna primary sources, Battle of Pydna 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 Pydna”?
- Who created the surviving record, and for what administrative purpose?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “Battle of Pydna” 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.