DWG RG-S13243Server sheetchecked 40d ago
TestServer
Offline 90.156.214.152: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 TestServer, and is it up?
The current state of TestServer is offline, with the last sighting 40 days 6 hours ago. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. First seen by Rust Graphs on 18 September 2026.
In which location is TestServer hosted?
A region is not published by TestServer. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 90.156.214.152:28015.
What Rust version is recorded for TestServer?
On Windows, TestServer runs Rust network protocol 2633 and build 164530. To join, your game must be on the same protocol; Steam handles the update.
Player data
What player count is recorded on TestServer?
The latest refresh records TestServer as offline, last seen 40 days 6 hours ago.
Against other Rust servers, where is TestServer placed?
Player hours over seven days place TestServer at #13,243, within the top – of ranked servers.
Schedules
On TestServer, when do wipes occur?
Too few wipes are on record for TestServer to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 40 days 7 hours ago.
Rules and settings
Which rules and settings are recorded for TestServer?
The name of TestServer records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Community. Anti-cheat: VAC, from Valve, is on.
Lists and filters
Where does TestServer appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry TestServer are: Rust community servers, plotted. It is returned by these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meaning is attached to each tag on TestServer?
Tags published by TestServer, and read by the game's server browser: 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): Your game must match protocol 2633 to join; cs164530 (Build): 164530 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
How to join
How is TestServer joined?
Enter client.connect 90.156.214.152: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.