Local Test
Offline 193.32.126.176:28015 checked 11d 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 71% 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
- 17/ 100
- 289/ 400
- 172/ 225
- 132/ 100
- 354/ 1000
- 27/ 700
Quick answers
Tags and listings
Where does Local Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Local Test: 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; Last wipe: In the last 2 weeks.
How should you read the tags on Local Test?
The server browser shows these tags for Local Test: gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): It holds 2 players; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166494 (Build): It's on build 166494; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): The plugin framework here is 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
Where can you find Local Test?
No region comes from Local Test. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 193.32.126.176:28015.
How reliable is Local Test?
The server Local Test is not reachable at the moment; the last sighting was 11 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 7 October 2026.
What Rust version is Local Test on?
Rust network protocol 2634 and build 166494 is what Local Test runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
When does Local Test wipe?
Too few wipes are on record for Local Test 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. This world has been running since 11 days 6 hours ago.
Settings and map
What settings and rules have been applied to Local Test?
The name of Local Test contains no gather rate. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC is off: Valve's anti-cheat is not active.
Which map is active on Local Test?
A procedural map, generated by the game, is in play on Local Test.
Player count
Is Local Test busy?
Right now Local Test is offline, with its last appearance 11 days 6 hours ago.
What position does Local Test hold in the server rankings?
For player hours in the last seven days, Local Test ranks #15,961, within the top 71% of ranked servers.
Getting in
How do you get into Local Test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 193.32.126.176:28015.