Pinned Tweet
Check out this awesome item from @MemorySteelUA. It's a stylish piece of a Russian T-72 tank No 583 destroyed during The Battle for Kyiv in early 2022. What a cool way to support a Ukrainian company. My followers can get a 10% discount with the promo code STEEL10, valid for 24 hours on the website memorysteelua.shop/
Radio & Nukes 🇺🇦 retweeted
Huhh, so this is what a supersonic sea-skimming target interception looks like (Unseen IR cam Footage from US navy).
USS Philippine Sea & USS Mason engaging a GQM-163A Coyote target using AEGIS combat system and SM-2 interceptors during SWATT training in the Atlantic.
Radio & Nukes 🇺🇦 retweeted
Pakistan announced nuclear explosions at two sites in 1998: five at Ras Koh on May 28, then another in the Kharan Desert on May 30. @CoreyAH identified where the Kharan shot likely happened. I processed 1998 SPOT & LANDSAT imagery and ... she's right! Clear ground disturbance.
I pulled the public orbital elements on all three satellites in the viral "SpaceX froze a NATO spy satellite so Russia could intercept it" brief and ran the numbers myself. The data shows two ordinary things happened. The explosive story welded onto them isn't supported, and in specific, checkable places it's flatly false.
WHAT ACTUALLY HAPPENED (public Space-Track elements, SGP4):
1) A Russian inspector satellite, COSMOS 2612, made a close co-orbital approach to the commercial radar satellite ICEYE-X36. It closed to tens of meters at ~0 m/s on 16-18 Oct, then withdrew. Same orbital plane (incl 97.85°), and it actively maneuvered to get there. This is a real, notable Russian proximity operation. It required ZERO SpaceX involvement, because Russia tracks and maneuvers with its own sensors.
2) A Starlink (STARLINK-35856) had a routine conjunction with ICEYE-X36, ~0.45 km on 16 Oct 23:54 UTC. Real, but ordinary. Starlink sits in a totally different plane (incl 70° vs 98°), so this was a ~15 km/s crossing that lasts seconds. Every object in LEO gets these constantly.
That's the whole factual content. Everything else is refuted by the data or isn't an orbital measurement at all.
WHAT THE DATA REFUTES:
❌ "Intercept / immobilized / kill." All three satellites are on orbit and intact right now (elements epoch 25-26 Oct). ICEYE-X36 is alive and tracked. Cosmos 2612 withdrew to ~490 km and is still drifting away. A close approach that ends in withdrawal is an inspection, not a kinetic intercept.
❌ "X36 dodged a Russian approach in June, so it had to be frozen this time." Neither half happened. Cosmos 2612 never came within 50 km of X36 until 16 Oct. In June they were thousands of km apart. And X36 shows no June maneuver: smooth drag decay, with weekly averages falling from 546.1 to 545.0 km and a largest single step of -433 m (noise). A real 0.5 km avoidance burn would be a clean -500 m step. There is none.
❌ "SpaceX pinned/froze X36 in place." X36 never maneuvers, period. Over 165 days it deviates from its natural decay curve by no more than 278 m and holds inclination to 0.022°. There was nothing to "pin." It's a passively decaying microsat. For contrast, Cosmos 2612 shows a 47.8 km altitude burn in a single day. That is what a real maneuver looks like in the data.
❌ "SpaceX inflated the danger 5x, claiming the real distance was 1.9-2.0 km." Independent public elements give ~0.45 km for the Starlink pass, consistent with the ~0.4 km figure cited, not 1.9-2.0 km. That "5x safer" claim needs SpaceX's private ephemerides that no one outside SpaceX can see, and the public data points the opposite way.
CREDIT WHERE DUE: the brief's raw archive numbers are real. The TLE update gaps and the conjunction time match my own pull. But multi-hour public TLE gaps are routine for every LEO object, and SpaceX having good space tracking is public knowledge used for collision avoidance. Neither is evidence of collusion.
WHAT ORBITAL DATA CAN'T SETTLE: "coordination" with Russia, collision-alert intent, Starlink throttling, the 23% figure, Iran, finances. Those are assertions, not measurements. The brief's "99.9% probability" is that inference restated as a number, and several of its load-bearing inputs (the June evasion, the 5x inflation, "X36 could maneuver") are false, so it's garbage in.
Orbital data can't prove a negative on intent. I can't prove no one coordinated. What I can show is that the data provides no evidence for it and contradicts the specific mechanisms claimed.
Bottom line: a real Russian satellite inspection, which was already public and known, plus a routine Starlink flyby. Two unrelated events, one narrative bolted on top.
All checks from public Space-Track two-line elements via SGP4. Happy to share the numbers.
SpaceX Blocked A U.S. And NATO Satellite to Assist a Russian Intercept After Crippling Ukraine's Air Defenses
The Math Proves the Reality that Musk doesn't want you to see.
On Oct 13-14, SpaceX restricted Starshield/Starlink during a 39-missile Russian attack, cutting Ukrainian drone intercepts by 23% and stranding U.S. personnel in Kyiv. Forty-eight hours later (Oct 15), SpaceX blocked U.S.-licensed NRO, Space Force, and NATO radar satellite ICEYE-X36 in orbit so Russia's COSMOS 2612 weapon could intercept it (99.89%-99.98% posterior)
Our Model Demonstrates that the Russian intercept of the US/NATO ICEYE X-36 satellite (contemporaneous with the throttling of Starlink) would not have been possible, and almost certainly not been attempted, without SpaceX resources. At a material opportunity cost, Russia sprinted its COSMOS satellite to intercept ICEYE X36. Based on a previous attempt in June during which X36 maneuvered to evade COSMOS, Russia knew that this would be successful only if X36 could not maneuver. On October 15, SpaceX fixed X36 in place by issuing a collision alert for a sub-kilometer approach with its Starlink 35856 when SpaceX's own data shows that the actual distance was 4.8-5.0x as great. SpaceX issued no warning to COSMOS despite the fact that its sprint was far more threatening than the stable X36 orbit. SpaceX did not maneuver its Starlink 35856 satellite to clear the supposed collision risk. How, absent coordination with SpaceX, could Russia have known that SpaceX would take actions that (a) misrepresented the danger posed by X36, and (b) resulted in the fixing of X36 thereby enabling COSMOS's successful intercept? Thus, SpaceX was directly involved in simultaneously compromising Ukraine’s defensive and offensive capabilities. The conjunction of these two events makes innocent explanations untenable.
The Pentagon Capture & Iran Round Two Trap: Pentagon CTO Emil Michael who cashed out $7M–$35M from Musk’s inner-circle SpaceX vehicles (M8/Gigafund 0.1 and M6/Valor M33 II) and KQ Partners / xAI (selling xAIfor $5M–$25M three days before taking over CDAO/OSCand 21 days before SpaceX bought xAI, while keeping M8, M6, M9, M10 & Nomadic open) and Pete Hegseth purged rival Anthropic in two hours, surrendered combat command over US drones used to attack Iran to Starlink’s "Terms of Service," and on October 2 named Musk Co-Director of Project Meridian to design the Pentagon's "Future of Warfighting" just as America enters Iran Round Twowith depleted Patriot/THAAD magazines and Russia feeding U.S. warship/aircraft locations to Tehran.
SpaceX’s actions in Ukraine raise serious questions about its alignment with US security interests and its reliability as a cornerstone of US defense. These questions are particularly troubling given the effectively irreplaceable position SpaceX has been granted by the Hegseth/Emil Michael Pentagon.
$SPCX $TSLA
Our full quantitative analysis below w/ @streetwiseprof
Radio & Nukes 🇺🇦 retweeted
💥🚀 New footage released by local residents shows strike by eight Ukrainian Storm Shadow cruise missiles during the October 25 attack on Russia’s Energia plant in Yelets.
Missiles slam into the same spot one after another, with no visible air defense response. Witnesses claim eight missiles struck the facility.
Energia produces batteries for Russian missiles, aircraft, and other military equipment.
Combined with the October 23 Storm Shadow strike on Proton in Oryol, the scale of these attacks suggests Ukraine may have received a substantial new shipment of the missiles.
Radio & Nukes 🇺🇦 retweeted
3D-LiDAR
active collision avoidance, obstacle detection, autonomous indoor navigation...
Radio & Nukes 🇺🇦 retweeted
‼️Uwaga! Alert RCB‼️
„UWAGA! Rosyjski atak powietrzny na terenie Ukrainy. Sytuacja jest monitorowana. W przestrzeni RP operuje polskie lotnictwo. Oczekuj dalszych komunikatów.”
Alert RCB został wysłany do odbiorców na terenie części województwa:
- lubelskiego - powiaty: puławski, opolski, Lublin, lubelski, kraśnicki, janowski, włodawski, łęczyński, świdnicki, Chełm, chełmski, krasnostawski, hrubieszowski, Zamość, zamojski, tomaszowski, biłgorajski, łukowski, Biała Podlaska, bialski, rycki, radzyński, parczewski, lubartowski.
Radio & Nukes 🇺🇦 retweeted
Data centers have become targets in war. From Europe to the Middle East, recent strikes show how these expensive facilities can be vulnerable to cheap aerial threats.
See more satellite imagery from @vantortech of wartime damage to data centers here: viewsfromabove.bradyafrick.c…
Radio & Nukes 🇺🇦 retweeted
ICEYE and @Nokia announced today a partnership with The Ministry of Defence of Ukraine to develop sovereign satellite communications. ICEYE has supported Ukraine since 2022 and delivers sovereign space capability at speed. This builds on that.
Read more: hubs.li/Q04C3bj-0
Radio & Nukes 🇺🇦 retweeted
A rare view of concerning activity in orbit.
From Oct. 16–18, a Russian satellite made several close approaches to a U.S. commercial satellite. This image, collected by Vantor’s WorldView Space capability on Oct. 17, shows Russian Cosmos 2612 at an estimated distance of about 1 km from ICEYE-X36.
“This image captures a reality long recognized by our national security leaders—space is becoming increasingly contested. Seeing one spacecraft repeatedly maneuver close to another raises serious concerns about capability and intent.”—Dan Smoot, Vantor CEO.
With WorldView Space, Vantor’s non-Earth imaging capability lets us collect images of other spacecraft in orbit, helping us better understand how they’re operating and spot activity that warrants a closer look.
Read @axios's exclusive coverage: axios.com/2026/10/22/space-w…
Explore WorldView Space: vantor.com/product/worldview…
🛰️ Right now, a Russian satellite is flying in close formation with a Western commercial-ish radar satellite, and makes another close pass in the next ~10 minutes.
COSMOS 2612 has matched orbits with ICEYE-X36, a Finnish-built commercial-ish radar (SAR) satellite. They're circling the planet together under half a kilometer apart, making a close pass almost every orbit (~95 min), the next one around 01:38 UTC (18 Oct), every one at essentially zero relative velocity.
Being upfront: at these separations (sub-km, down to tens of meters), the exact distance is below the precision of public tracking, so treat specific metre figures as indicative. What ISN'T ambiguous is the orbit match and the ~0 m/s closing. This is deliberate, controlled formation flying, the behaviour associated with close-up inspection, not a chance conjunction (collision).
And it's targeted. Cosmos 2612 is the ONLY one of a six-satellite cluster (Cosmos 2609–2614) to have maneuvered: it raised its orbit in the public data ~47 km, drifted into phase with X36, then dropped back to settle alongside it. The other five never moved.
As just announced in the @UN First Committee, Russia’s COSMOS 2612 military satellite has been exhibiting threatening behavior by intentionally maneuvering dangerously close to a commercial satellite, behaviors consistent with on-orbit weapons operations. This violates long-established safety thresholds in low Earth orbit. The United States will continue to secure and defend American vital national security interests in, from, and to space.
Radio & Nukes 🇺🇦 retweeted
As just announced in the @UN First Committee, Russia’s COSMOS 2612 military satellite has been exhibiting threatening behavior by intentionally maneuvering dangerously close to a commercial satellite, behaviors consistent with on-orbit weapons operations. This violates long-established safety thresholds in low Earth orbit. The United States will continue to secure and defend American vital national security interests in, from, and to space.
Radio & Nukes 🇺🇦 retweeted
‼️Uwaga! Alert RCB‼️
„UWAGA! Rosyjski atak powietrzny na terenie Ukrainy. Sytuacja jest monitorowana. W przestrzeni RP operuje polskie lotnictwo. Oczekuj dalszych komunikatów.”
Alert RCB został wysłany do odbiorców na terenie woj. lubelskiego.
Radio & Nukes 🇺🇦 retweeted
Saudi Arabia: Iranian-supported Houthis have engaged in hostilities against Saudi Arabia, including attacks on civilian airports and other critical infrastructure resulting in civilian casualties and severe travel disruptions. The hostilities have the potential to escalate rapidly beyond that immediate area. U.S. citizens are reminded to follow the guidance of national alerts released by Saudi Arabia’s Civil Defense via cellular broadcast. Operations at King Khalid International Airport in Riyadh remain suspended. King Abdulaziz International Airport in Jeddah and King Fahd International Airport in Dammam are operational with some delays and cancellations. U.S. citizens should be aware of potential attacks on airports, airspace closures, flight cancellations, and travel disruptions. Please take extreme caution if you choose to use airports in Saudi Arabia. We recommend checking your flight departure status directly with the airline and with the airport. More at: sa.usembassy.gov/security-al…
PHP PIFFFFF, no more tax money for PHP 😂🤣
🚨 Organizations should immediately patch critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619. These vulnerabilities enable unauthenticated #RCE and affect PHP installations serving web requests. Learn more: 🔗 go.dhs.gov/5Hi
Radio & Nukes 🇺🇦 retweeted
EXCLUSIVE: In a joint investigation by @InsiderGeo × @SONARROW_OSINT , we identified a large-scale Russian military loading operation in Baltiysk. Between October 15 and 16, we observed the Russian cargo vessels ASCALON (IMO 9198226), LADY D (IMO 9349289) and ANASTASIIA (IMO 9349291) loading significant quantities of military equipment at the Kaliningrad naval base, including logistics vehicles, infantry vehicles, MRAPs and troop transports.
A rotation of other cargo vessels also appears to have taken place in the days before and after, although heavy cloud cover over the period makes this difficult to confirm.
One or more large convoys are likely already underway. Their destination(s) remain unknown at this time.
Radio & Nukes 🇺🇦 retweeted
1/2 The number of confirmed air defense towers and ramps in Alabuga, the main production facility for Russian strike drones, has reached 33, as a new @planet high-res image taken today, Oct. 21, shows. Ukraine hasn’t attempted to strike the site since June 2025.
Radio & Nukes 🇺🇦 retweeted
I think, I found the same kind of radar tower in the area of
"333rd Radio-Technical Regiment military unit 17646-B"
in Fornosovskoye gorodskoye poseleniye, Leningrad Region
59.536853, 30.650316
already built before April 2024.
Best public image [2]: bing.com/maps/search?cc=de&s…











































