Ukrainian UAV operator Dmytro is used to seeing war through a drone camera. From cover, he saw people and equipment on the other side of the front, chose the moment to attack, and remained almost invisible himself. But during a brief exit from his position, he heard a Russian quadcopter above him. Dmytro ran and opened fire upwards—now he was the one being hunted. He described this episode to Financial Times journalists in the autumn of 2025. For one person, it was a chance encounter in a forest belt. For the entire war, it was a sign of a systemic turning point.

Russian drones had attacked Ukrainian operators before. What was new was the scale and the choice of priority. The Rubikon Center for Advanced Unmanned Technologies began systematically searching not only for equipment on the front line but also for what makes the Ukrainian drone system cease to function: crews, antennas, communication devices, repair points, and supply transport. A destroyed drone can be replaced in a day. A trained operator who knows the terrain, frequencies, neighboring units, and the specifics of their own equipment is significantly harder to replace.

This is where the main change brought by Rubikon lies. Its strength is not in a single secret drone or a spectacular individual video. Russia created an organization capable of connecting reconnaissance, combat application, analysis, testing, production, and training into a single repeating cycle. A frontline discovery ceased to be the property of one successful team and could become a practice for dozens of units. But by 2026, this same conveyor belt faced a contradiction: the faster it expanded, the more actively it drew rare specialists from regular units, and the harder it became to maintain the quality for which the center was created.

A Unit Created Outside the Regular Army

Rubikon's official history began on August 2, 2024. The new Minister of Defense, Andrey Belousov, ordered the creation of the center based on an already existing combat unmanned aviation unit. It was publicly announced in October, after Belousov's visit. The Russian military department then described the structure with an almost ideal formula: it simultaneously tests equipment, trains operators and instructors, analyzes experience, and implements new solutions in the troops.

Behind this promotional construct lay a real problem. In the first years of the full-scale war, the Russian drone ecosystem grew from the bottom up. Field workshops, volunteers, small teams of operators, and private manufacturers changed frequencies, software, and drone designs faster than the large army. But the results remained uneven. A strong team could gain a new capability, while a neighboring brigade continued to operate under old rules. The military vertical was good at distributing approved models but struggled with technologies that changed faster than the procurement cycle.

Rubikon was allowed to act as an exception within the system. According to the reconstruction by researchers Rob Lee and Dmitry Putyata from the Foreign Policy Research Institute, the center received priority funding, payments at the level of special forces units, the ability to select personnel, and direct access to manufacturers. Combat crews relayed feedback to developers without a long chain of approvals, received modified equipment, and tested it again at the front. In a regular unit, a problem would go through reports and headquarters; here, it could immediately become a technical specification.

Thus, an organization emerged that outwardly resembled a military unit but functionally resembled a testing ground, a training center, a design bureau, and a combat formation all at once. Its composition included analysts, software developers, communications and electronic warfare specialists, instructors, repair personnel, and combat detachments. Such a structure did not abolish the bureaucracy of the entire army. It created a protected corridor within which individual solutions moved faster.

Why the Target Became Not the Drone, But the Person Behind the Controls

Rubikon's public videos create the impression of an endless catalog of strikes. However, more important than the number of frames is the change in the structure of targets. According to data cited by RFE/RL, referencing an open dataset from the pro-Kremlin project LostArmour, by September 2025, over a quarter of the center's published strikes targeted Ukrainian drones, and about 15 percent more targeted radars, communications, and electronic warfare equipment. This is not a complete statistic of combat operations: it only includes published episodes, and the rules for video selection are unknown. But even this dataset shows a priority—to strike not only the ultimate target but the very infrastructure of drone warfare.

This logic is more dangerous than the usual hunt for machines. An operator needs power, communication, repairs, regular delivery of drones, and the ability to move positions. If one FPV is destroyed, the unit loses a consumable. If operators are forced to abandon a convenient point, supply is disrupted, and antennas are disabled, the effectiveness of dozens of future sorties simultaneously drops. Rubikon began to work precisely on these dependencies.

The effect is confirmed not only by Russian statements. In September 2025, RFE/RL quoted Ukrainian servicemen and independent analysts who called the center's work methodical and systemic. In one episode, according to Rob Lee, a Ukrainian brigade reported losing up to 70 percent of its operators in a specific sector in one week. It is impossible to verify this figure with open data, so it cannot be extrapolated to the entire front. But it explains why Ukrainian commanders publicly called Rubikon an adversary that needed to be studied separately.

The Financial Times described the same change through the experience of operators near Pokrovsk. Russian crews worked continuously, could change shifts, and maintained pressure around the clock. Ukrainian crews had to reduce movements, change positions more often, and spend part of their resources not on supporting their infantry but on searching for Russian operators. Thus, Rubikon achieved results not only through direct hits. It forced the enemy to change behavior—and therefore reduced the amount of time they could dedicate to their own tasks.

Sudzha and Pokrovsk: Where the Conveyor Became Noticeable

The first major episode after which the center became known outside a narrow circle of specialists was the Kursk region. In early 2025, several Rubikon detachments focused on the supply routes of the Ukrainian grouping in the Sudzha area. RFE/RL and FPRI link their work to systemic pressure on transport and logistics before the withdrawal of Ukrainian forces in March. It would be incorrect to attribute the result to a single structure: Russian regular units, North Korean military personnel, aviation, and artillery were operating simultaneously. But Rubikon demonstrated a model for reinforcing a priority direction—quickly assembling several specialized detachments and assigning them a common task deeper than the usual operating zone of brigade FPVs.

In the summer and autumn of 2025, this model was transferred to the Pokrovsk, Myrnohrad, and Kostiantynivka direction. According to FPRI, several detachments of the center were operating there simultaneously, including formations redeployed from other sectors. Their task was to increase pressure on logistics, communications, and Ukrainian drone positions. The Institute for the Study of War described what was happening as a partial aerial isolation of the battlefield: Russian drones complicated the delivery of resources and created conditions for the penetration of small infantry groups.

The word "partial" is fundamental here. The saturation of the direction with strong drone units helped Russian troops advance but did not ensure a rapid operational breakthrough. FPRI notes that even the concentration of several Rubikon detachments did not allow Russia to develop its penetration east of Dobropillia into a decisive success. The Ukrainian command stabilized the sector by redeploying strong units and its own unmanned units. Drones changed the conditions of battle but did not negate infantry, engineering support, reserves, and quality of command.

This distinction shatters two equally convenient legends. Russian propaganda presents Rubikon as an almost independent weapon of victory. Its opponents sometimes cite the lack of a breakthrough as proof of the center's failure. Both conclusions are incorrect. At the tactical level, the center could significantly worsen the situation of specific Ukrainian units. At the operational level, its result depended on the entire grouping. Rubikon proved to be an amplifier—dangerous, but not self-sufficient.

How an Elite Experiment Was Turned into a Mass Structure

In the spring of 2025, Rubikon could still be described as a network of small elite detachments. According to FPRI's reconstruction, there were eight such formations in April. Six were assigned to the main Russian troop groupings, and two more were subordinate to the joint command. The staff of a typical detachment was 149 people, with actual manning averaging about 85 percent.

Then the center began to grow in two dimensions at once. The number of combat formations increased to 17 detachments, two battalions, and six companies. Simultaneously, the estimated staff of one typical detachment was raised from 149 to 474 people. It included more of its own command, reconnaissance, communication, repair, and support elements. This provided autonomy: the detachment was less dependent on the brigade it was temporarily reinforcing. But along with autonomy, the need for officers, engineers, technicians, and communication specialists grew—precisely those people who are difficult to train en masse.

The total strength of Rubikon, according to FPRI's estimate, grew from approximately 1,450 people at the end of March 2025 to 5,000 in the spring of 2026. The approved staff reached 9,000. Researchers estimated the headquarters at approximately 175 people, seven research and functional units at 270, and the training and support circuit at 700. Most of the rest served in combat units. These figures are not an official census but show the direction of the reform: Moscow was deploying not a compact center for disseminating experience, but a large combat formation.

Such a choice changes the meaning of the organization. While an experienced group tests a solution and trains other units, it multiplies knowledge. When this same group turns into dozens of its own crews, it has to consume most of the trained personnel itself. The center, which was supposed to cure the army's unevenness, begins to compete with the army for the same people.

The Price of Speed: Who Rubikon Takes

In the early stages, the right to choose the best was an advantage. Rubikon could transfer already cohesive teams from motorized rifle regiments and brigades to itself. For the center, this was the fastest way to acquire an experienced crew. For the donor unit, it was a loss not only of several servicemen. Along with them went knowledge of the sector, working connections with reconnaissance and artillery, repair skills, and informal supply channels. A new crew can be assigned by order, but accumulated experience cannot be instantly restored.

FPRI directly indicates that Rubikon's further expansion occurred at least partially at the expense of regular formations and could weaken their own reconnaissance and unmanned fire support. The researchers simultaneously emphasize: this is not an exclusively Russian problem. With the expansion of Ukraine's "Drone Line," strong teams also transferred from maneuver brigades to specialized units, temporarily leaving their former units weaker. The dilemma is common to both armies—concentration increases quality in a chosen location but reduces its uniformity along the front.

For Russia, the risk is amplified by the speed of administrative growth. Staff can be approved in a day, but rare qualifications cannot. When an organization increases severalfold in a year, the number of experienced instructors does not grow at the same rate. New people have to be selected less stringently, and older ones are more often used for training and management instead of frontline work. As a result, expansion increases the number of crews but can lower their average level.

Varyag and the Redistribution of Scarcity

By 2026, Rubikon faced another competitor—the very reform for which it served as a model. Russia was simultaneously deploying the 50th Unmanned Systems Brigade "Varyag." The former commander of Rubikon, Sergey Budnikov, headed the new formation. Along with him, according to FPRI's assessment, about 600 people were transferred to the 50th Brigade.

This episode is important not as an internal intrigue, but as an indicator of the system. An organization created to concentrate expertise itself became a personnel donor. Rubikon and Varyag received growing tasks but competed for the same market of people: operators, engineers, developers, communication specialists, and instructors. Competition can accelerate experiments, but without sustainable knowledge exchange, it turns reform into a tug-of-war of ready-made teams between new signboards.

The scale of the problem is much larger than one center. FPRI estimated the strength of Russian Unmanned Systems Troops at approximately 87,000 people by the end of 2025, with a plan for 165,000 by the end of 2026. To replenish, tens of thousands of contract soldiers were expected to be recruited, and thousands more servicemen transferred from other units. However, Russia was already failing to meet monthly recruitment plans. The broader the new structure, the more likely its growth will be ensured not by creating specialists, but by redistributing existing ones.

On August 5, 2026, Vladimir Putin appointed Denis Lyamin as commander of the Unmanned Systems Troops and instructed him to complete their formation. The appointment finally solidified the institutional shift: drones are no longer an auxiliary function of individual units, but a separate military vertical. But along with status, the new branch of service inherited Rubikon's contradiction—headquarters and staff grow faster than experience.

What the Russian Army Actually Achieved

Rubikon's main result is not the stated number of sorties or the compilation of destroyed equipment. Such figures are poorly comparable: one sortie can end without an attack, several drones can work on one target, and published video does not always allow for determining the outcome. The center's real achievement is organizational. The Russian army received a mechanism that, faster than the usual vertical, transforms a problem from the front into a test, equipment modification, training module, and new practice.

This system has already influenced the war. Ukrainian units are forced to protect operators more seriously, change positions more often, separate control elements, and allocate resources for counter-drone warfare. In certain directions, Rubikon helped reduce freedom of movement and increased pressure on supplies. To ignore this as propaganda would be dangerous.

But it is equally erroneous to believe that Moscow has solved the problem of adaptation for the entire army. The center remains a privileged exception, and its expansion shows how difficult it is to turn an exception into a norm. To create more strong detachments, the system takes people from regular units. To maintain a high pace, it lowers the selection threshold. To deploy a new branch of service, it fragments already accumulated expertise among parallel formations.

Conclusion: A Conveyor Belt That Hit a Human Wall

Rubikon proved that the Russian military machine is capable of learning faster than commonly believed. In two years, a small experiment turned into a multi-thousand-person structure, its detachments began operating in the most important directions, and the developed model became part of a new branch of service. This is not a promotional facade or just another name for an old unit.

But the center's history simultaneously shows the limit of Russian centralization. Money can buy equipment. An order creates a headquarters. A production line can be expanded. An experienced operator, engineer, or instructor cannot be produced by administrative decision. The faster Rubikon is transformed from a laboratory into a mass formation, the more actively it consumes the rare human capital that ensured its initial success.

Therefore, the main question is no longer how many detachments the center will have and how many videos they will publish. The question is whether the system can reproduce qualifications faster than it expands staff and divides specialists among new structures. So far, the answer is ambiguous. Rubikon helped Russia turn frontline experience into a conveyor belt. But the conveyor belt itself hit a resource that cannot be stocked in a warehouse—people.