Offline2.63.25.148:28015checked 27d ago
TEST
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 bestWipe 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageSettings and map
Which rules govern TEST?
A gather rate is absent from the name of TEST. Groups are capped at 8 players, the default in the game. The server runs survival, gather, build, raid: the standard game. Fighting and raiding between players is allowed. Under Community in the server browser, it is a community server. Anti-cheat VAC from Valve is on.
Which map is running on TEST?
A procedural map, generated by the game, runs on TEST.
Tags, lists and filters
Where can TEST be found in Rust Player Count lists and filters?
These Rust Player Count lists include TEST: Best Rust PvE servers. You can find it on the server list using these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you interpret the tags on TEST?
For the game's server browser, TEST publishes: gmrust (Game mode): The usual Rust survival experience; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team, which is what the game sets by default; v2633 (Protocol): To join, your game must match protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): No region code is set. The tags also include its current players, its queue and when its world was made, shown at the top of this page.
Population
How full is TEST?
TEST is offline at the moment; the last time it was seen was 27 days 6 hours ago.
What position does TEST hold among Rust servers?
Over the last seven days, TEST is #13,352 for player hours, placing it in the top – of ranked servers.
Server information
What is the uptime and reliability of TEST?
TEST is down at the moment and was last seen 27 days 6 hours ago. In the last 7 full days, it was up for 0 of 168 hours, which is 0% uptime. Rust Player Count recorded it for the first time on 16 September 2026.
What Rust version is used on TEST?
On Windows, TEST runs Rust network protocol 2633 and build 163794. Joining requires the same protocol on your game; Steam updates it for you.
What region does TEST serve?
No region is published by TEST. Rust Player Count displays the location a server claims, not the physical location of the machine. You can reach it at 2.63.25.148:28015.
Wipe days
What wipe pattern does TEST follow?
The rhythm of wipes on TEST cannot be told yet, since too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe arrives, wiping every Rust server. It has been running its current world for 27 days 8 hours.
Connect to the server
How can I connect to TEST?
Joining is done by opening the console (F1) and running client.connect 2.63.25.148:28015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.
Server tags
what each one meansPublished 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.