# C O M P L E T E G A R B A G E on Mizan

Banned on 8 lists, 7 in force.

- Platform: Steam
- SteamID64: 76561198235723668
- SteamID: STEAM_0:0:137728970
- SteamID (CS2): STEAM_1:0:137728970
- SteamID3: [U:1:275457940]
- SteamID32: 275457940
- Hex (FiveM): steam:1100001106b2794
- Checked: 11 November 2026
- Page: https://mizan.ac/players/steam/76561198235723668
- JSON: https://mizan.ac/players/steam/76561198235723668.json

## Steam's Record

This read of the record doesn't include Steam's VAC and game bans.

## Bans

Each ban is the claim of the list that made it, and each reason is in that list's words.

- 10 July 2016, Second Generation \(SG-Gaming\) (staff decision): "FV1". Team Fortress 2. In force.
- 16 June 2016, Xeno Gamers (staff decision): Cheating. "SMAC 0.8.5.1: Aimbot Detected". Team Fortress 2. In force.
- 15 June 2016, Horizon Servers (staff decision): "player dis". Counter-Strike: Global Offensive. Expired 16 June 2016.
- 5 June 2016, FirePowered Gaming (staff decision): Cheating. "\(Duplicate of another account\) Aimbot". Team Fortress 2. In force.
- 29 May 2016, KZTimer GlobalAPI \(CS:GO KZ\): Cheating. "bhop\_hack". Counter-Strike: Global Offensive. In force.
- 28 May 2016, Neon Heights (staff decision): "\[SourceSleuth\] Player is IP banned on a different account". Team Fortress 2. In force.
- 21 May 2016, Panda Community (staff decision): "Auto Airblast". In force.
- 13 August 2015, Disc-FF \(SourceBans TF2\) (staff decision): Cheating. "Aimbot". Team Fortress 2. In force.

## Disputing a Ban

A ban is appealed to the community that published it. How: https://mizan.ac/disputes