local-test
Offline 168.220.162.128:28015 checked 6d 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 72% 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
- 291/ 400
- 199/ 225
- 124/ 100
- 396/ 1000
- 37/ 700
Quick answers
Tags and listings
Where does local-test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry local-test are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
What's the meaning of the tags on local-test?
The server browser shows these tags for local-test: gmrust (Game mode): This is the standard Rust survival experience; mp2 (Max players): The slot count is 2; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167398 (Build): It's on build 167398; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^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.
About the server
What location is local-test in?
There is no published region for local-test. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 168.220.162.128:28015.
How reliable is local-test?
local-test is down at the moment; it was last up 6 days 22 hours ago. In the last full 6 days, 0 of 144 hours were online, 0% uptime. 11 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for local-test?
On Windows, local-test runs Rust network protocol 2634 and build 167398. The protocol must match to join; Steam will update your game.
Wipe details
When does local-test wipe?
The wipes recorded for local-test are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 6 days 22 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is local-test running?
The name of local-test 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. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
Which map is active on local-test?
The map on local-test is procedural, made by the game.
Player stats
What's the population like on local-test?
Right now local-test is offline, with its last appearance 6 days 22 hours ago. Across the last seven days, the typical count has been 0 players.
Where does local-test sit in the rankings?
For player hours in the last seven days, local-test ranks #15,797, within the top 72% of ranked servers.
Getting in
How do you get into local-test?
To join, open Rust, hit F1, and enter client.connect 168.220.162.128:28015. Or click Launch Rust on this page to open the game through Steam and connect.