TEST
Offline 95.158.36.201:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 wipes- 577/625
- 32/250
- 73/250
- 290/325
- 114/200
- 120/150
Quick answers
from the figures on this pageWipe timing
How often does TEST wipe, and when?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 40 days 16 hours ago the current world was made.
Tags
How should you read the tags on TEST?
Tags published by TEST, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TEST?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #14,815, in the top – of all ranked servers.
How full does TEST get?
Reading for TEST: offline at this moment; last seen 40 days 16 hours ago.
Server
What location is TEST hosted in?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 95.158.36.201:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 163794 on Windows, run by TEST. To get in, your game needs the same protocol; Steam applies the update.
Is TEST up, and how often does it stay up?
Check: connection. TEST is offline at this moment. Last contact was 40 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 17 September 2026.
Rules and settings
What settings and rules apply on TEST?
Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Connection
How do you connect to TEST?
Press F1 in Rust and enter client.connect 95.158.36.201:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.