FANDOM


1st Special Armored Battalion
1. Spezialpanzerbataillons
Mazu Tokushu Sōkō Daitai
Active April 26, 1945–Present
Country Template:Country data Nazi Germany (formerly)

Template:Country data Empire of Japan (formerly)
Template:Country data United States

Allegiance Allied Powers
  • Office of Strategic Services
  • United Allied Armies
Role Mechanized and armored warfare
Combined arms warfare
Expeditionary warfare
Size 750
Commanders
Current
commander
Borealis Norsoutha
Notable
commanders
Ushanka Mosin Aleksandr Zoborov

Miho Nishizumi

The 1st Special Armored Battalion was an Allied tank unit dedicated for special operations.

HistoryEdit

The battalion has its beginnings during World War II when word that a gate leading to another world was discovered by OSS operatives. After a base was established, Allied and OSS commanders decided to create a battalion dedicated to handle the German threat on the other side.

As well, there are notable defections from the Axis powers. Waffen S.S. commander Borealis Norsoutha and his crew were among a few of them during Operation: Virus House, the battle to stop the plans of German commander Graf von Schrader. In the Pacific, a special Japanese tank crew led by Miho Nishizumi followed suit during the Battle of Manila in February 1945. With those in place, the idea of a multi-national battalion manned with defectors and veteran Allied crewmembers became possible.

Operation: Arch MageEdit

The first combat operations were conducted during the push to Sadera from their starting point in Italica. Encountering decent German resistance, they suffered only little casualties and they moved on.

During the Battle of Sadera, the battalion became one of the spearheads in the liberation knocking out multiple tanks and, most especially, a single Maus super-heavy tank at the cost of few of their own.

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.