Local Test
Offline 183.94.166.217:28015 checked 42d ago
Server instruments
no direct query in 48 hoursPlayers now
100% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 280/350
- 24/250
- 37/250
- 138/200
- 50/200
- 44/100
Quick answers
from the figures on this pageWipe timing
How often does Local Test wipe, and when?
Its rhythm cannot be told from the wipes of Local Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 42 days 9 hours ago the current world was made.
Tag meanings
Which tags does Local Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Local Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Local Test?
Rust Metrics lists featuring Local Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does Local Test sit in the rankings?
Player hours over seven days put Local Test at #14,448, in the top – of all ranked servers.
How full does Local Test get?
Local Test is not responding; status offline, last seen 42 days 9 hours ago.
Server
Where does Local Test sit?
Reading: location. Local Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 183.94.166.217:28015.
What Rust version is Local Test on?
Reading: Local Test, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Local Test, and is it online now?
Local Test reports offline. The last reading came 42 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does Local Test enforce, and what are its settings?
Check: gather rate. The name Local Test does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is Local Test on?
Check: map. Procedural, generated by the game, on Local Test.
How to join
What do you do to join Local Test?
Press F1 in Rust and enter client.connect 183.94.166.217:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.