TEST
Offline 83.149.37.29:28015 checked 27d 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 bestTop 65% 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- 47/500
- 124/100
- 62/225
- 58/700
- 15/200
- 17/1000
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes 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 it runs now was made 38 days 4 hours ago.
Tags
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TEST: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,455, in the top 65% of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 27 days 23 hours ago.
Server details
Which location does TEST run from?
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 83.149.37.29:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on TEST, and is it online?
Check: connection. TEST is offline at this moment. Last contact was 27 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 30 September 2026, recorded by Rust Metrics.
Map and rules
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
Connection
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 83.149.37.29:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.