What happened

On 19 October 2026, UNIAN reported an assessment by Andrii Kolesnyk, a former adviser to the head of Ukraine’s State Space Agency who had worked on analysis and forecasting of space activity, that Russia was no longer maintaining the intended launch cadence for the Rassvet constellation.

Kolesnyk noted that the first 16-satellite production batch launched on 23 March and the second on 19 July. By 19 October, three months after the July mission, a third production batch had not been reported in orbit.

He said Russia had intended to launch groups of 16 satellites at a substantially faster cadence and estimated that at least 130 functioning spacecraft would be needed for broadband coverage across Ukraine, implying roughly nine Soyuz-2.1b launches at 16 spacecraft per mission. The exact operational constellation size remains contested, with other Ukrainian assessments using higher figures.

Kolesnyk said the delay could be connected in part to Ukraine’s August strike on the Progress Rocket Space Centre in Samara, which assembles Soyuz launch vehicles, but he did not present evidence establishing that the strike caused the missing third launch. He also offered an alternative explanation: Bureau 1440 may be preparing a more advanced Rassvet spacecraft generation incorporating lessons from the first two production batches.

Evidence and limitations

The strongest new evidence is the observable launch sequence. The two reported 2026 production missions occurred on 23 March and 19 July, and no third production-batch launch had been reported by 19 October. This establishes a gap of at least three months after the July mission without requiring an inference about its cause.

The claim that Russia intended monthly 16-satellite launches comes from Kolesnyk’s assessment rather than a newly published Bureau 1440 launch manifest. It should therefore not be treated as a verified contractual schedule. Earlier public Russian plans described rapid constellation expansion but have varied in the number of spacecraft and timing.

The suggested connection to the August strike on Progress is plausible but unproven. LAT-RU-RAS-0003 records Ukraine’s confirmation that the 15 August strike hit a Soyuz-related production workshop at Progress, while noting that the extent of damage and any programme impact were not independently established. The absence of a third Rassvet launch does not by itself demonstrate that the strike caused the delay.

Kolesnyk’s suggestion that Russia may instead be preparing a Rassvet-4 generation is also speculative. Bureau 1440 separately confirmed in September that it had begun work on a new generation of spacecraft, recorded in LAT-RU-RAS-0010, but no public evidence cited here establishes that a new generation is responsible for the current launch gap.

Confidence: High for the launch dates and the absence of a reported third production launch by 19 October; moderate that the deployment cadence is slower than intended; low for any specific causal attribution to the Progress strike or a transition to a new spacecraft generation.

Assessment

The missing third launch is the first concrete opportunity to test earlier warnings that industrial constraints could slow Rassvet deployment. It does not prove that the programme has suffered a lasting disruption, but it weakens assumptions that the constellation will expand at a regular high-frequency cadence.

The development is especially relevant because spacecraft attrition is occurring at the same time. Two satellites from the July batch are in rapidly decaying low orbits, as recorded in LAT-RU-RAS-0020. A slower replenishment cadence combined with individual spacecraft losses would make the path to continuous coverage longer than a simple count of planned launches suggests.

Attribution remains important. The August Progress strike, launch-vehicle availability, ongoing flight testing, spacecraft redesign, production constraints or ordinary mission scheduling could each contribute to the gap. Current public evidence does not distinguish among them.

Why it matters

Rassvet’s operational trajectory depends not only on whether individual satellites function but on how quickly Bureau 1440 can repeatedly place production batches into orbit. Launch cadence determines how rapidly intermittent communication windows can become persistent regional coverage.

The three-month-plus gap therefore provides a measurable deployment indicator against which the six-month continuous-coverage estimate recorded in LAT-RU-RAS-0022 can be tested. A resumed launch sequence would reduce the significance of the present delay; a continuing gap would increasingly support the view that launch or production capacity is constraining deployment.

It also creates a clearer framework for assessing the effect of Ukrainian strikes on space-industry infrastructure. Rather than treating a strike as proof of programme disruption, subsequent launch timing can provide observable evidence of whether industrial damage translates into sustained operational delay.

Sources

  • UNIAN, 19 October 2026 — interview with former Ukrainian State Space Agency adviser Andrii Kolesnyk on the launch cadence, the outstanding third batch and possible explanations for the delay.
  • Slovo i Dilo, 20 October 2026 — subsequent Ukrainian reporting describing the same launch-cadence shortfall and the potential relevance of strikes on Russian space-industry facilities.