DWG RG-S15050Server sheetchecked 44d ago
TEST
Offline 188.19.173.245:28015 checked 44d 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
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
Server data
What uptime is recorded for TEST, and is it up?
Last seen 44 days 13 hours ago; right now TEST is offline. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. On 14 September 2026 is when Rust Graphs first saw it.
What location is recorded for TEST?
No region is published by TEST. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 188.19.173.245:28015 is its address.
On which Rust version is TEST running?
On Windows, TEST runs Rust network protocol 2633 and build 163794. The same protocol is required for joining, and Steam updates your game to it.
Player data
What player count is recorded on TEST?
No response from TEST; the server was last seen 44 days 13 hours ago.
In the rankings, which position does TEST hold?
Within the top – of all ranked servers: TEST at #15,050 for player hours, seven days recorded.
Wipe data
Which times and days are wipes plotted at on TEST?
The record of TEST's wipes is too short to tell its rhythm. 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 44 days 13 hours ago.
Settings
Which settings does TEST run, and what rules?
Gather rate for TEST: not stated in the name. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. It appears under Community in the server browser. VAC is on: that is Valve's anti-cheat.
What is the map for TEST?
A procedural map, generated by the game, is what TEST runs.
Filters
On Rust Graphs, which lists and filters contain TEST?
These Rust Graphs lists include TEST: 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.
Which meaning is attached to each tag on TEST?
The game's server browser reads these tags from TEST: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team limit is 8, which is the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs163794 (Build): Build: 163794; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
By what method do you join TEST?
Connect with client.connect 188.19.173.245:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
ts8
v2633
cs163794
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.