Skip to content

Player Lookup

Steam profile

STEAM_0:0:24167139876561198443608524

  • Steam

Steam didn't answer in time. Look again in a moment for the name and picture.

Banned for cheating by Rushy Servers

First banned on 8 Feb 2018.

Steam's record

Not read this time.

VAC banned
Not read
VAC bans
Not read
Game bans
Not read
Since last ban
Not read
Trade ban
Not read
Community ban
Not read

Bans2

Past bans on 1 list, none in force.

As of 2 Nov 2026, Rushy Servers had a cheating ban on this account; it is no longer in force.

Rushy Servers

Staff decision2
Bans from Rushy Servers, in force first, newest first
BannedReason, in the list's wordsWhereLengthState
CheatingYou were voted off due to cheating/another reason. This lasts 30 minutesTeam Fortress 230 minutesEnded 11 Feb 2018
CheatingYou were voted off due to cheating/another reason. This lasts 30 minutesTeam Fortress 230 minutesEnded 8 Feb 2018

Each list published its own bans, and every reason is in its words. Mizan copies them as published and enforces none. Think a ban is wrong?

More bans on Rushy Servers

Every ban on Rushy Servers
  • noSTEAM_0:1:227985305

    SMAC 0.8.6.0: AutoTrigger Detection: BunnyHop

    Team Fortress 2

    22 August 20171 hour

  • not a smurfSTEAM_0:1:221308935

    SMAC 0.8.6.0: AutoTrigger Detection: Auto-Fire

    Team Fortress 2

    14 August 20171 hour

  • WaterSTEAM_0:0:222263470

    SMAC 0.8.6.0: AutoTrigger Detection: BunnyHop

    Team Fortress 2

    4 August 20171 hour

  • j1648046STEAM_0:1:224088603

    SMAC 0.8.6.0: AutoTrigger Detection: BunnyHop

    Team Fortress 2

    30 July 20171 hour

  • Anime NiBBaSTEAM_0:1:221885953

    SMAC 0.8.6.0: AutoTrigger Detection: BunnyHop

    Team Fortress 2

    18 July 20171 hour

  • -BHOP MASTER-STEAM_0:0:221967375

    SMAC 0.8.6.0: AutoTrigger Detection: BunnyHop

    Team Fortress 2

    14 July 20171 hour

The players Rushy Servers banned most recently, each reason in its own words.