local-test
Offline 168.220.162.128:28015 checked 18d ago
Vital stats
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
Top 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
| 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.
Quick answers
From the figures on this page.
Server tags
Which Rust Pop Watch lists and filters include local-test?
These are the Rust Pop Watch lists that include local-test: Modded Rust servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on local-test mean?
The game's server browser picks up these tags from local-test: gmrust (Game mode): Plain vanilla Rust survival, nothing bolted on; mp2 (Max players): Slots: 2; ts8 (Group limit): This uses the default limit of 8 players per team; v2634 (Protocol): You need the same game version to get in: protocol 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): The network layer is RakNet, which is the game's standard; $r? (Region code): Region code left blank; ^o (Oxide): A plugin framework called Oxide (uMod) is running here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
Player counts
How does local-test rank against other Rust servers?
A seven-day player-hours placing of #15,790 puts local-test in the top 71% of all ranked servers.
How many players are on local-test right now?
The last sighting of local-test was 18 days 19 hours ago, and it is offline now.
Server facts
Is local-test online, and how reliable is it?
Down at the moment: local-test was last seen 18 days 19 hours ago. Out of 168 hours in the last 7 full days, it was online for 0, a 0% uptime. Rust Pop Watch's first record of it is 11 October 2026.
Where is local-test located?
No region is published by local-test. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 168.220.162.128:28015.
Which Rust version is local-test on?
On Windows, local-test runs Rust network protocol 2634 and build 167398. To join, your game must be on the same protocol; Steam handles the update.
The wipe schedule
What is the wipe schedule on local-test?
local-test's rhythm stays hidden while so few of its wipes are on record. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. The world it is running now dates from 18 days 19 hours.
The rules
Which map does local-test run?
local-test uses a procedural map, which the game generates.
What are the rules and settings on local-test?
Nothing in the name tells you the gather rate on local-test. Eight players per group: that is the game's default. survival is the game mode, the usual game of gathering, building and raiding. Raids and PvP are both on the table. The server browser files it under Modded, where plugins or settings change the game. Oxide plugins are running on it. Anti-cheat is on: VAC, Valve's system.
Getting in
How do I join local-test?
Enter client.connect 168.220.162.128:28015 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.