Ukraine's Commander-in-Chief Valerii Budanov issued a statement on September 11 reaffirming Kyiv's resolve to continue military operations for as long as necessary. The statement, reported via Telegram, emphasizes that Ukraine will pursue fighting until its strategic objectives are achieved. No specific operational details or timeline were provided in the brief statement.
Budanov's reaffirmation comes amid sustained Russian drone pressure on Kyiv and surrounding areas. On September 10–11, Ukrainian air defense tracked multiple Russian Shahed-136 kamikaze drones transiting toward the capital region, prompting air raid alerts and defensive posturing. While no impacts were reported from those particular drone runs, the tempo of Russian strikes on Kyiv reflects Moscow's continued effort to degrade Ukrainian morale and military capacity. Public statements by senior Ukrainian commanders are often calibrated messaging—directed at both domestic and international audiences—and typically indicate leadership assessment that military continuation remains strategically viable despite pressure.
Single source: Telegram channel @ClashReport. Confidence score of 7.0 reflects that the statement itself—as a public utterance by a named official—is inherently verifiable, though reliance on one channel limits immediate cross-confirmation. Confidence would rise with republication by major news outlets or official Ukrainian military channels; it would lower if the statement were disputed or redacted.
Kyiv, the Ukrainian capital and seat of national command authority, located in Kyiv Oblast in north-central Ukraine at approximately 50.45°N, 30.52°E. The statement was issued from the capital's administrative and military center, the natural platform for statements by the Commander-in-Chief.
▶ View this event on the live map
Intel Mapper aggregates open-source reports from monitored Telegram and X channels, geolocates them, cross-checks duplicates across sources and assigns a confidence score. Entries are updated as new confirmations arrive. Read how we verify events.