Local_Test
190.114.39.185:28015 checked 26d 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 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
Quick answers
Map and rules
Which settings and rules apply on Local_Test?
No gather rate appears in the name Local_Test. The group cap is 8 players, the default for the game. It runs survival, gather, build and raid: the standard game. You can fight and raid other players here. You will find it under Community in the server browser. VAC is off, Valve's anti-cheat.
Which map is active on Local_Test?
The game generates the procedural map Local_Test runs.
Player count
What is the population like on Local_Test?
At present, Local_Test is offline and its last appearance was 26 days 23 hours ago.
What is Local_Test's ranking?
For player hours over the last week, Local_Test is #15,420, which puts it in the top – of all ranked servers.
Tags and filters
What do Local_Test's tags indicate?
What the game's server browser gets from Local_Test is this tag list: gmrust (Game mode): Survival in the standard Rust mode; mp10 (Max players): Capacity: 10; ts8 (Group limit): The team cap is 8, which is the game's default; v2633 (Protocol): To join, your game must match protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left unset. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.
Which Rust Zerg Life filters and lists cover Local_Test?
Rust community servers for clans: that is where you will find Local_Test among the Rust Zerg Life rankings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server info
How reliable is Local_Test, and is it up?
No sign of Local_Test at present: it was last seen 26 days 23 hours ago. Over the last 7 full days, uptime was 0%: 0 hours up out of 168. Its first appearance in Rust Zerg Life records is 18 September 2026.
What version is Local_Test using?
On Windows, Local_Test runs Rust network protocol 2633 and build 164530. The protocol must match for you to join, and Steam will update your game to that protocol.
Where can you find Local_Test?
There is no region published by Local_Test. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 190.114.39.185:28015.
Wipe days
When does Local_Test wipe?
The record of Local_Test's wipes is too thin to reveal its rhythm. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. The world it is running now dates from 26 days 23 hours ago.
How to join
What is the process to join Local_Test?
Join by entering client.connect 190.114.39.185:28015 in the console (press F1 first). Or use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp10
ts8
v2633
cs164530
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.