Test
Offline 83.142.15.36:28015 checked 38d ago
Server instruments
no direct query in 48 hoursPlayers now
33% 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- 581/575
- 365/400
- 37/250
- 44/250
- 164/200
- 74/100
Quick answers
from the figures on this pageWipe schedule
How often does Test wipe, and when?
The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 52 days 19 hours ago.
Tag meanings
Which tags does Test carry, and what do they mean?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp3 (Max players): Slots: 3; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; 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.
Player count
Where does Test sit in the rankings?
Player hours over seven days put Test at #13,979, in the top – of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 38 days 14 hours ago.
Operator and location
Which location does Test run from?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 83.142.15.36:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 164530 on Windows is the build Test runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Check: connection. Test is offline at this moment. Last contact was 38 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.
Rules and settings
What settings and rules apply on Test?
No gather rate appears in the name: Test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
Check: map. Procedural, generated by the game, on Test.
Join
What do you do to join Test?
Press F1 in Rust and enter client.connect 83.142.15.36:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.