Testing Shit
Offline 92.40.217.35:28015 checked 16d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 0/ 100
- 72/ 400
- 51/ 245
- 120/ 100
- 90/ 1000
- 6/ 700
Quick answers
Tags and listings
Where does Testing Shit appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Testing Shit are: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Testing Shit?
gmrust (Game mode): Survival, as standard Rust does it; mp0 (Max players): It holds 0 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166493 (Build): This server runs build 166493; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — that is the tag list Testing Shit puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What's the location of Testing Shit?
Testing Shit does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 92.40.217.35:28015.
What's the uptime like for Testing Shit?
Testing Shit is down at the moment; it was last up 16 days 14 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 1 October 2026.
What is the Rust version for Testing Shit?
Rust network protocol 2634 and build 166493 is what Testing Shit runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
How often does Testing Shit wipe?
Too few wipes are on record for Testing Shit to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 16 days 14 hours is how long ago this world came into being.
Map and rules
Which rules and settings is Testing Shit running?
The name of Testing Shit contains no gather rate. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
Player count
How many players are on Testing Shit?
Testing Shit was last seen 16 days 14 hours ago and is offline as you read this.
Where does Testing Shit sit in the rankings?
Over the last seven days, Testing Shit is #16,408 by player hours, among the top 69% of all ranked servers.
Join info
What's the way to join Testing Shit?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 92.40.217.35:28015.