TST15339=
TEST
Online 121.80.41.68:28015 checked 6m ago
Players
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 UTC10d 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.
-
01MODPlayers 1/100
-
02MODPlayers 0/100
-
03MODPlayers 1/69
-
04MODPlayers 0/100
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show TEST?
On Rust Tracker, TEST sits in these lists: PvE servers, tracked live, Modded servers, tracked live, Combat training servers, tracked live and Build, creative and sandbox servers. On the server list, these filters bring it up: 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.
How should you read the tags on TEST?
The game's server browser reads these tags from TEST: gmvanilla (Game mode): Vanilla survival is the mode; mp3 (Max players): Slots: 3; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^d (Combat training): Practice aim and PvP; the loot is handed to you; ^k (Build server): Practise base building and design; ^p (PvE): PvE: the world threatens you, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Schedule
What happens on TEST on wipe day?
The average peak across recent wipes: 1 players. The peak on the latest wipe came 0 hours after it.
Which wipe times are confirmed for TEST?
TEST's rhythm cannot be told yet: too few wipes on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 10 days 11 hours since this world was made.
Location and Status
What is the uptime on TEST, and is it online?
TEST is up and online at this moment. The uptime it reports puts the last restart about 10 days 10 hours ago. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. First contact for Rust Tracker: 17 October 2026.
Which Rust build is TEST running?
Confirmed for TEST: Rust network protocol 2634 and build 167781, Linux. To join, your game must be on the same protocol; Steam handles the update.
How smoothly does TEST run?
Server fps held an average of 60 across the last 48 hours, never below 58. Buildings, deployables and the rest of the world took it to a maximum of 133,552 entities. It drew as much as 8,607 MB of memory. Players feel lag when fps drops and the entity count climbs.
Which location is TEST in?
Region: none published by TEST. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 121.80.41.68:28015.
Player Count
What is the player count on TEST?
Slots 3; players on board 0: that is TEST now. Seven-day average for this server: 0 players.
How does TEST compare in the rankings?
Seven-day player hours put TEST at #15,339, within the top 69% of all ranked servers.
Settings
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. 8 players per group is the game's default, and the cap holds. It runs combat training, aim practice and PvP, loot given out. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.
Which map is confirmed for TEST?
The map on TEST is procedural, size 4,500, seed 823183683, generated by the game. Same size, same seed, same map. RustMaps shows it, linked from this page.
Connect
Which steps join TEST?
To connect: start Rust, press F1, enter client.connect 121.80.41.68:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published as mp3,ptrak,$r?,v2634,^d,^k,^p,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
mp3
ts8
v2634
cs167781
ptrak
$r?
Gameplay
^d
^k
^p
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.