test
Offline 83.196.166.124:28015 checked 11d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 bestTop 70% 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
the same kind of game, then region, group limit, rate and wipes- 248/275
- 21/250
- 16/250
- 170/200
- 64/200
- 37/100
Quick answers
from the figures on this pageReset cycle
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 11 days 20 hours ago.
Tag meanings
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; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show test?
These Rust Metrics lists carry test: 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; Last wipe: In the last 2 weeks.
Occupancy
What position does test hold among Rust servers?
Player hours over seven days put test at #15,114, in the top 70% of all ranked servers.
What is the population on test?
Reading for test: offline at this moment; last seen 11 days 19 hours ago.
Operator and location
Which location does test run from?
Reading: location. test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 83.196.166.124:28015.
What Rust version is test on?
Reading: test, Rust network protocol 2634 and build 167781, Windows. 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 11 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 October 2026, recorded by Rust Metrics.
Rules and settings
What rules does test enforce, and what are its settings?
Reading the name gives no gather rate for test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is test on?
The game generates a procedural map for test.
Connection
How can you get onto test?
Press F1 in Rust and enter client.connect 83.196.166.124:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.