DWG RG-S13861Server sheetchecked 23d ago
test
Offline 91.108.0.163:28015 checked 23d 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 61% 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
What uptime is recorded for test, and is it up?
test is offline at this moment; 23 days 18 hours ago is when it was last seen. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 4 October 2026.
What location is recorded for test?
There is no region published by test. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 91.108.0.163:28015 is its address.
On which Rust version is test running?
On Linux, test runs Rust network protocol 2634 and build 166652. The same protocol is required for joining, and Steam updates your game to it.
Counts
How many players are plotted on test?
test is not responding at the latest refresh; the last record of it online is 23 days 18 hours ago.
Against other Rust servers, where is test placed?
Within the top 61% of all ranked servers: test at #13,861 for player hours, seven days recorded.
Wipe data
Which times and days are wipes plotted at on test?
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 current world has been in use since 26 days 11 hours ago.
Rules and settings
Which rules and settings are recorded for test?
Gather rate for test: not stated in the name. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Community is its tab in the server browser. VAC is on: that is Valve's anti-cheat.
On which map is test played?
test runs a procedural map, which the game generates.
Filters
On Rust Graphs, which lists and filters contain test?
The Rust Graphs lists that carry test are: 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.
Which meaning is attached to each tag on test?
gmrust (Game mode): Standard survival, as Rust plays; mp75 (Max players): Slots: 75; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty 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.
Connect
What is the way to connect to test?
In Rust, press F1 and type client.connect 91.108.0.163:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
Server tags
Published as mp75,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
mp75
ts8
v2634
cs166652
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.