DWG RG-S13285Server sheetchecked 40d ago
TEST
Offline 95.170.182.48:28015 checked 40d 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 40 days 3 hours ago; right now TEST is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. First seen by Rust Graphs on 17 September 2026.
What location is recorded for TEST?
No region is published by TEST. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 95.170.182.48:28015.
What Rust version is recorded for TEST?
Rust network protocol 2633 and build 164530 on Windows: that is what TEST runs. The same protocol is required for joining, and Steam updates your game to it.
Population
What does the population history show for TEST?
The latest refresh records TEST as offline, last seen 40 days 3 hours ago.
What rank has been recorded for TEST?
Over the last seven days, TEST records #13,285 for player hours: the top – of all ranked servers.
Wipe data
Which times and days are wipes plotted at on TEST?
Too few wipes are on record for TEST to show its rhythm. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 40 days 4 hours ago the current world was made.
Rules and settings
What settings and rules apply on TEST?
No gather rate is stated in the name of TEST. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. The server browser lists it under Community. Anti-cheat: VAC, from Valve, is on.
Which map has TEST loaded?
A procedural map, generated by the game, is what TEST runs.
Lists and filters
On Rust Graphs, which lists and filters contain TEST?
These Rust Graphs lists include TEST: Rust community servers, plotted. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
On TEST, what is meant by each tag?
gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): To join, your game must be on protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded are the tags TEST publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Joining the server
How is TEST joined?
Enter client.connect 95.170.182.48:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it 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.