Rainbow Six Wiki


695pages on
this wiki
Add New Page
Comments0 Share
Rainbow Six Siege Icon "A lot of eyes are on us this time, especially since we have poor intel."
This article, SASG-12, is a stub and may require expansion. Please help out by editing the page.

The Saiga-12 is a semi-automatic shotgun manufactured by Kalashnikov Concern (Formerly Izhmash).[1]

The SASG-12 is categorized as a shotgun in the Rainbow Six universe. The SASG-12 appears in Tom Clancy's Rainbow Six Siege, and the Saiga-12 was a weapon that was cut from the final products of both Tom Clancy's Rainbow Six: Vegas and Tom Clancy's Rainbow Six: Vegas 2.

Tom Clancy's Rainbow Six: Vegas 1 & 2

The Saiga-12 is a weapon that was supposed to be featured in both Tom Clancy's Rainbow Six: Vegas and Tom Clancy's Rainbow Six: Vegas 2, but was later cut from the final product. This weapon was found among the files of the PC versions of both games.

Tom Clancy's Rainbow Six Siege

"Semi-automatic shotgun, favored by Spetsnaz. Limited range, large spread decreases accuracy."
— In-game description

The SASG-12 is a weapon featured in Tom Clancy's Rainbow Six Siege. It is available for use by Spetsnaz Recruits and Operators Kapkan and Tachanka.


The SASG-12 is one of the most potent, close-ranged, semi-automatic shotguns next to the SPAS-12. In terms of damage and fire rate, this magazine-fed shotgun can easily tear an Operator to pieces, though long-range is inadvisable, but that goes without saying. It's still a powerful weapon even with a Suppressor, which brings the damage on par with the other semi-automatic shotguns.

Weapon Attachments

Under Barrel


Tom Clancy's Rainbow Six Siege

  • Even though the description of the weapon states the weapon to hold 8 rounds in its magazine, the magazine capacity is actually 10 rounds in-game. This has since been fixed.

Patch Changes


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.