test
91.108.0.163:28015 checked 9d 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 bestTop 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
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
Server rules
Which settings and rules apply on test?
No gather rate appears in the name test. That is the game's default: groups of up to 8 players. survival is its mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. Community is its section in the server browser. VAC is on, Valve's anti-cheat.
Which map is active on test?
The game generates the procedural map test runs.
Server population
What is the population like on test?
The server test is currently offline; it was last seen 9 days 22 hours ago.
What position does test hold in the server rankings?
In the top 61% of ranked servers, test holds #13,861 for player hours over the last seven days.
Server tags
What do test's tags indicate?
The game's server browser reads these tags from test: gmrust (Game mode): Standard survival gameplay; mp75 (Max players): Capacity: 75; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): It runs build 166652; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left unset. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.
Where does test appear in Rust Zerg Life lists?
The Rust Zerg Life lists that include test are Rust community servers for clans. 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; Last wipe: In the last 2 weeks.
Server info
How reliable is test, and is it up?
No sign of test at present: it was last seen 9 days 22 hours ago. Across the last 7 full days, 0 of 168 hours were online, which is 0%. The first time Rust Zerg Life saw it was on 4 October 2026.
Which Rust build does test use?
On Linux, test runs Rust network protocol 2634 and build 166652. You can only join if your game uses the same protocol, and Steam takes care of updating it.
What location does test use?
There is no region published by 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 91.108.0.163:28015.
Wipe cycle
How often does test wipe, and on what days?
So few of test's wipes are recorded that its rhythm cannot be told yet. 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 12 days 14 hours ago.
How to join
What is the process to join test?
Enter client.connect 91.108.0.163:28015 in the F1 console. Another way: use Launch Rust on this page, which opens Rust 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.