Battle of Skopje
1004 battle near the Bulgarian city of Skopje
The Battle of Skopje was a battle in 1004 during the Byzantine reconquest of Bulgaria. The campaign was carried out in a slow and systematic manner, with campaigns sometimes continuing year-round rather than following the traditional seasonal pattern. The primary reason for mounting a long campaign was the realization by Basil II that Bulgaria could not be conquered in a single campaign. Instead the emperor chose to employ systematic and constant pressure, resulting in gaining control over crucial fortresses. He first secured Sardika (modern Sofia) and then advanced north to sever Samuil's access to the former Bulgarian heartlands around Preslav. Once this area was under control, Byzantine forces moved south from Sardika into Macedonia, capturing Berrhoia and reopening the route to Greece. Byzantine authority was soon restored in Thessaly and in parts of eastern Macedonia, including Voden. Basil then launched a major offensive northward toward the Danube, culminating in the capture of Vidin after an eight-month siege. During this time, Samuil personally led a raid through the reconquered territories and briefly seized Adrianople, which he plundered but was unable to hold.
Background
In 1003, Basil II launched a campaign against the First Bulgarian Empire and after eight months of siege conquered the important town of Vidin to the north-west.
The public source identifies “Battle of Skopje” as 1004 battle near the Bulgarian city of Skopje. This brief keeps that definition visible, then builds a research path around Battle, Skopje and battle.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Battle of Skopje”, the useful work is to connect “1004 battle near the Bulgarian city of Skopje” to the records capable of establishing context and consequence.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q1896360. Authority coordinates are 42.000, 21.433. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1004 and 1003.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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
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 “Battle of Skopje”, its source revision and the description used here.
- Expand the search: follow Battle of Skopje primary sources, Battle of Skopje 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 Skopje”?
- 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 “Battle of Skopje” 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.