Testing Shit
Offline 92.40.217.34: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
- 87/ 400
- 50/ 245
- 132/ 100
- 91/ 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.
What's the meaning of the tags on Testing Shit?
The server browser shows these tags for Testing Shit: gmrust (Game mode): Survival, as standard Rust does it; mp0 (Max players): It holds 0 players; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166493 (Build): It's on build 166493; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is Testing Shit in?
Testing Shit does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 92.40.217.34:28015.
How reliable is Testing Shit?
Testing Shit is down at the moment; it was last up 16 days 13 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 1 October 2026.
What is the Rust version for Testing Shit?
The version on Testing Shit is Rust network protocol 2634 and build 166493, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
How often does Testing Shit wipe?
Testing Shit's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 16 days 14 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is Testing Shit running?
The name of Testing Shit contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Player stats
Is Testing Shit busy?
The last sighting of Testing Shit was 16 days 13 hours ago; it is offline right now.
Where does Testing Shit sit in the rankings?
Over the last seven days, Testing Shit is #16,413 by player hours, among the top 69% of all ranked servers.
Getting in
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.34:28015.