# FLCL on Mizan

Banned on 8 lists, all in force.

- Platform: Steam
- SteamID64: 76561198346792371
- SteamID: STEAM_0:1:193263321
- SteamID (CS2): STEAM_1:1:193263321
- SteamID3: [U:1:386526643]
- SteamID32: 386526643
- Hex (FiveM): steam:11000011709edb3
- Checked: 5 November 2026
- Page: https://mizan.ac/players/steam/76561198346792371
- JSON: https://mizan.ac/players/steam/76561198346792371.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.

- Undated, midnight cheater list, Nocrex/Tom \(TF2\): Cheating. "Marked as a cheater". Team Fortress 2. In force.
- Undated, rijin cheater list, Nocrex/Tom \(TF2, L4D2\): Cheating. "Marked as a cheater: TOO MANY INFRACTIONS, OB PITCH". Team Fortress 2. In force.
- 16 June 2026, Nemesis.surf \(TF2 Bot Detector list\): Cheating. "Marked as a cheater". Team Fortress 2. In force.
- 8 December 2024, vorobey hackerpolice \(TF2 Bot Detector list\): Cheating. "Marked as a cheater". Team Fortress 2. In force.
- 2 February 2019, TF2 Oreon (staff decision): Cheating. "SMAC 0.8.5.1: AutoTrigger Detection: BunnyHop". Team Fortress 2. In force.
- 27 January 2019, TauriGaming.cz (staff decision): Cheating. "Aimbot". Team Fortress 2. In force.
- 1 August 2017, Panda Community (staff decision): Cheating, Exploiting. "Healing exploit/hack". In force.
- 12 April 2017, BlackWonder.TF (staff decision): Cheating. "SMAC 0.8.6.0: Aimbot Detected". Team Fortress 2. In force.

## Disputing a Ban

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