DWG RG-S13219Server sheetchecked 34d ago
Local_Test
Offline 86.174.170.175:28015 checked 34d 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
Top 57% 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
Quick answers
Recorded details
How reliable is Local_Test, and is it online now?
Last seen 34 days 19 hours ago; right now Local_Test is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 22 September 2026 is when Rust Graphs first saw it.
In which location is Local_Test hosted?
A region is not published by Local_Test. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 86.174.170.175:28015 is its address.
What Rust version is recorded for Local_Test?
Rust network protocol 2633 and build 165217 on Windows: that is what Local_Test runs. To join, your game must be on the same protocol; Steam handles the update.
Player data
How many players are plotted on Local_Test?
The latest refresh records Local_Test as offline, last seen 34 days 19 hours ago.
Against other Rust servers, where is Local_Test placed?
Within the top 57% of all ranked servers: Local_Test at #13,219 for player hours, seven days recorded.
Schedules
Which times and days are wipes plotted at on Local_Test?
Local_Test's rhythm cannot be told yet: too few of its wipes are on record. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 34 days 20 hours ago.
Map and rules
Which settings does Local_Test run, and what rules?
No gather rate is stated in the name of Local_Test. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. It appears under Community in the server browser. Anti-cheat: VAC, from Valve, is off.
On which map is Local_Test played?
A procedural map, generated by the game, is what Local_Test runs.
Lists and filters
On Rust Graphs, which lists and filters contain Local_Test?
On Rust Graphs, Local_Test is placed in these lists: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
On Local_Test, what is meant by each tag?
The game's server browser reads these tags from Local_Test: gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): Your game must match protocol 2633 to join; cs165217 (Build): 165217 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
How to join
How is Local_Test joined?
In Rust, press F1 and type client.connect 86.174.170.175:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
Server tags
Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp10
ts8
v2633
cs165217
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.