Second battle of Su City
Main Info
Date September 19th 2504
Place Su City (Sukhoi)
Result USR Victory

AVS forces retreat from Sukhoi

Major Battles Air strike at Talwk

Battle of Su city Metropolis

Desert Kraigon

Force 1 United Sapphirian Republics
Force 2 Adariin Viserak Systems
Force 3 -
Force 4 -
Leader 1 Wertias Opop / Yosev Starris
Leader 2 Raark Spherianus
Leader 3 -
Leader 4 -
Army 1 Epsilon Squadron

Delta Squadron

Gamma Squadron

Army 2 4880th Fleet

515th Fleet

Army 3 -
Army 4 -
Deaths 1 Light
Deaths 2 Heavy
Deaths 3 -
Deaths 4 -
Previous First Battle of Su City
Next Battle of Marc Canyon
This was the last battle on the planet Sukhoi .


After the USR was pushed back by AVS after the battle of Su City, USR was able to send in Delta Squadron to assist, Arcto Archon was frustrated with the Delta Squadron officer "Shadana Mara " he and his force left and headed back to Shrine to make an appeal, but instead he landed on Kall and began preparations for the arrival of the TEC . Meanwhile the USR prepared themselves for the battle on Sukhoi, DS Commander Yosev Starris ordered a Night raid against the Viserak .

Delta Squadron began the attack on September 19th, they caught the sleeping Viserak off guard and destroyed ther first base, DS, ES and GS forces poured into the region via Troopship and drove the Viserak to the center of the city.

Wertias Opop demanded a surrender, Spherianus refused and continued resistance, he soon escaped as his forces were defeated in the city center, the bulk of the Viserak army in the city became prisoners of war. After this battle, any continued fighting was minor. The USR learned that surprise attacks were superior to guerrilla warfare or standard warfare when fighting the Viserak, Sukhoi was also the first planet completely retaken by the USR during the Sector wars .

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.