Emona
ancient city in Roman Italia, now Ljubljana

Emona (early Medieval Greek: Ἤμονα) (or Aemona [short for Colonia Iulia Aemona]) was a Roman castrum, located in the area where the navigable Nauportus River came closest to Castle Hill, serving the trade between the city's settlers – colonists from the northern part of Roman Italy – and the rest of the empire.
Emona was the region's easternmost city, although it was assumed formerly that it was part of the Pannonia or Illyricum, but archaeological findings from 2008 proved otherwise.
The Visigoths camped by Emona in the winter of 408/9, the Huns attacked it during their campaign of 452, the Langobards passed through on their way to Italy in 568, and then came incursions by the Avars and Slavs. The ancient cemetery in Dravlje indicates that the original inhabitants and invaders were able to live peacefully side by side for several decades. After the first half of the 6th century, there was no life left in Emona. The 18th-century Ljubljana Renaissance elite shared the interest in Antiquity with the rest of Europe, attributing the founding of Ljubljana to the mythical Jason and the Argonauts. Other ancient Roman towns located in present-day Slovenia include Nauportus (now Vrhnika), Celeia (now Celje), Neviodunum (now the village of Drnovo) and Poetovio (now Ptuj).
History
During the 1st century BC a Roman military stronghold was built on the site of the present Ljubljana, below Castle hill. Construction of the Roman settlement of Emona, fortified with strong walls, followed in AD 14. It had a population of 5,000 to 6,000 people, mostly merchants and craftsmen.
“Emona” enters the record as ancient city in Roman Italia, now Ljubljana. Crown Archives preserves that source wording while asking what Emona, ancient and city can confirm, complicate or overturn.
Why this record matters
“Emona” is worth following because a concise public description often conceals a longer documentary argument. Here, Emona, ancient and city provides the most credible route into that argument.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Aug 21, 2026. The linked authority identifier is Q148327. Authority coordinates are 46.048, 14.501. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2008.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Emona”, its source revision and the description used here.
- Expand the search: follow Emona primary sources, Emona archive and Emona 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 “Emona”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Emona” 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.