TEST
Online 121.80.41.68:28015 checked 11m ago
Server instruments
last reading Wed 04:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 58 · below 20 is lag, below 10 is badEntities
48 h range 131,008–133,669 · memory 7,217 MBUptime
9 days 17 hours since its last restart, at the last readingPlayers
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, measured since 17 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 10:32 UTC9d ago | 1 | – | running | 1 |
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- 2/100
- 1/100
- 0/69
- 1/100
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on TEST?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 9 days 19 hours ago.
Tags
Which tags does TEST carry, and what do they mean?
Tags published by TEST, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp3 (Max players): 3 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^d (Combat training): Practise aim and PvP here; the loot comes to you; ^k (Build server): Design bases and practise building; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?
On Rust Metrics, TEST sits in these lists: Modded Rust servers, checked live, Aim training servers, live readings, Build and creative servers and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: PvE ^p, Combat training ^d, Build server ^k, Modded ^z and Oxide ^o; 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,257, in the top 69% of all ranked servers.
How full does TEST get?
Current headcount on TEST: 0 players, 3 slots available. Check: players over seven days. Average 0, peak 1.
Server
Which location does TEST run from?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 121.80.41.68:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167781, Linux. Matching protocol is required to join. Let Steam update your game.
How does TEST perform?
Check: fps. Average 60 server fps over the last 48 hours, low of 58. Within range. Peak entity count: 133,669. Buildings, deployables and all else included. Memory peak: 7,557 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is TEST, and is it online now?
TEST reports online. Status: normal. Reading: uptime. About 9 days 17 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 17 October 2026, recorded by Rust Metrics.
Rules and settings
How is TEST configured, and what rules are in force?
No gather rate appears in the name: TEST. 8 players per group, the default value. combat training, practice for aim and PvP, loot provided — that is the game mode. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
Size 4,500 and seed 823183683: the game generates the procedural map on TEST from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
How do you connect to TEST?
To join: start Rust, press F1 and type client.connect 121.80.41.68:28015. Or press Launch Rust here and Steam opens the game and connects you.