Kursk campaign
Ukrainian offensive into Russia's Kursk Oblast
On 6 August 2024, during the Russo-Ukrainian war, the Armed Forces of Ukraine launched an incursion into Russia's Kursk Oblast and clashed with the Russian Armed Forces and Russian border guard. A state of emergency was declared in Kursk Oblast, and Russian reserves were rushed to the area. By the end of the first week, the Ukrainian military said it had captured 1,000 km2 (390 sq mi) of Russian territory, while Russian authorities acknowledged that Ukraine had captured 28 settlements.
In the second half of August the front stabilized, and in early October, the Ukrainian advance had stalled. From November, North Korean forces were sent to the province to support the Russian military. By the end of that month, Russian forces recaptured around half of the territory Ukraine had occupied. By 11 March 2025, most of the Ukrainian forces appeared to have retreated as a result of a Russian counterattack. Russian troops entered Sudzha, around which a shrinking pocket of territory still controlled by Ukraine had formed, the next day.
Ukrainian officials said the goals of the operation included inflicting damage on Russia's military, capturing Russian troops, pushing Russian artillery further out of range, hindering Russian supply lines and diverting their forces from other fronts. It also aimed to put pressure on the Russian government and force it into "fair" peace negotiations.
This brief starts where responsible research should: with the source description of “Kursk campaign” as ukrainian offensive into Russia's Kursk Oblast. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as ukrainian offensive into Russia's Kursk Oblast. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Aug 26, 2026. The linked authority identifier is Q128686808. Authority coordinates are 51.191, 35.271. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2024 and 2025.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Kursk campaign”, its source revision and the description used here.
- Expand the search: follow Kursk campaign primary sources, Kursk campaign archive and Kursk 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 “Kursk campaign”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Kursk campaign” 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.