TBNSpace
Op-ed: Why Did Russia Bother with X36?
Publication: Payload
Author: Daniel Molland
Source published: 06/11/2026, 13:30:00 UTC
Briefing created: 06/11/2026, 13:59:06 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 06/11/2026, 13:50:26 UTC.
Briefings
A Russian military satellite, Kosmos 2612, conducted a close approach to an ICEYE radar satellite, X36, in late November 2025. This Space CTR mission was intended to characterize the radar's antenna for building a counter-jamming system. The operation occurred within a few hundred meters of X36, which has been sharing data with Ukraine since the 2022 war began. The US classified the approach as consistent with an on-orbit weapons operation, though analysts note Russia's use of five satellites for a five-month mission suggests a deliberate investment in intelligence gathering.
Key points
- A Russian military satellite, Kosmos 2612, conducted a close approach to ICEYE radar satellite X36 in late November 2025, operating dangerously close to the radar.
- The mission required significant investment in staffing and satellite lifetime, as Russia used five satellites to perform a five-month characterization mission.
Context
Russia's overriding operational aim is to achieve battlefield advantage in Ukraine by denying space-based intelligence, surveillance, and reconnaissance services. The US classifies the approach as consistent with an on-orbit weapons operation, while analysts note Russia's use of multiple satellites suggests a deliberate investment in intelligence gathering capabilities.
Limitations
The evidence covers a single specific mission and does not provide details on the jammer's deployment timeline, the specific frequency bands targeted, or the confirmed operational status of the jammer fielded by Russia.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 06/11/2026, 13:59:06 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeigcjkzbvrdlvcrfxeu3sr4iuftzum3xyxohpkfkl7acew2pcb7hyy