Skip to the story

Live edition33,807 playing on 11,590 servers

Rust Insights

Server profile

TEST

Online, with 0 of 3 players on; ranked #15,264 of every public Rust server, the top 69%. It last wiped 9d ago.

Filed under moddedoxidepve
Launch Rust and join
The server's own banner, as it publishes it.
0/ 3 players now 0% full
07-day averagepeak 1
#15,264ranktop 69%
9d agolast wipeno schedule published
–next wipetoo few wipes seen yet

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
0123406:0015:0000:0010:0019:0004:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

02040608006:0015:0000:0010:0019:0004:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k17 Oct19 Oct21 Oct24 Oct26 Oct28 Oct

Note: Top 69% of all ranked servers. Ranked on player hours over the last seven days.

The wipe cycle

Wipe schedule

Too few wipes seen yet.

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

1 wipe-day peak players, last three wipes

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

00.250.50.751+0h+9h+19h+28h+38h+47h

Note: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

The record

Wipes

Every wipe we saw, newest first.

WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 10:32 UTC9d ago 1 – running 1

Note: 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.

If you like this one

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. #1 Rust Saratov Relax [PVE|RaidBases|TP|Kits|Events|Bosses]groups of 8+ · biweekly · 4 on average1/100
  2. [TW][PVE]Strawberry Turkey PastaEA · groups of 8+ · monthly · 2 on average1/100
  3. Rusty XR Noobs | PvE or PvP with RaidControl | 10x+ | SlowDecaygroups of 8+ · 10x · monthly · 2 on average0/69
  4. RUST54 [RPG],[PVE&PVP],[ДЛЯ НОВИЧКОВ]EU · quad · monthly · 1 on average1/100

The short version

Quick answers

From the figures on this page.

Wipe cycle

What does TEST look like once wipe day arrives?

At their busiest, its recent wipes drew 1 players on average. 0 hours into the latest wipe, the crowd on the server reached its peak.

How often does TEST wipe, and on which day?

The record of TEST's wipes is too thin yet to show its rhythm. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. This world dates from 9 days 19 hours ago.

Server details

How well does TEST perform?

Average server fps over the last 48 hours was 60, with a floor of 58. The world held a peak of 133,669 entities, counting buildings, deployables and all the rest. It drew as much as 7,557 MB of memory. Lag, for players, is low fps and an entity count that keeps climbing.

Which Rust version is TEST on?

Running on Linux, TEST is on Rust network protocol 2634 and build 167781. You can only join if your game is on the same protocol; Steam handles that update.

What does uptime look like for TEST, and is it online?

At the time of this check TEST is online. Going by the uptime figure it gives, its last restart was around 9 days 17 hours ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. The first record Rust Insights has of it is 17 October 2026.

Where does TEST run from?

A region is not published by TEST. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. Connect through 121.80.41.68:28015.

Server tags

Which meanings sit behind the tags on TEST?

When the game's server browser reads TEST, it finds these tags: gmvanilla (Game mode): The mode is vanilla survival; mp3 (Max players): 3 slots in total; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2634 (Protocol): Your game must run the same version to join: the protocol is 2634; cs167781 (Build): Build 167781 is what it runs; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code field is empty; ^d (Combat training): A training ground for aim and PvP, with loot given out; ^k (Build server): Use it to design bases and practise builds; ^p (PvE): There is no player fighting; the world itself is the danger; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

Which Rust Insights filters and lists feature TEST?

The Rust Insights lists that carry TEST are Modded Rust servers, explained, Aim training servers, live, Rust build and creative servers and Rust PvE servers, live. On the server list, the filters that surface it are 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.

Player counts

What does the population of TEST look like?

TEST shows 0 players at the moment, against 3 slots. The seven-day average is 0 players, and the highest point in that week was 1.

Where does TEST sit in the rankings?

The player-hours ranking for the last seven days puts TEST at #15,264, among the top 69% of all ranked servers.

Map and rules

What are the settings and rules for TEST?

Nothing about gather rate is given in the name of TEST. The default of 8 players per group is what applies here. You get combat training as the game mode, aim and PvP practice, loot handed out. The server browser lists it under Modded: plugins or settings alter the game. Oxide is the plugin count it runs. Anti-cheat: VAC, from Valve, is on.

What is the map on TEST?

The game generates the map on TEST: procedural, size 4,500, seed 823183683. Size and seed give the same map each time, so this page lets you look at it on RustMaps.

Connecting

How do you connect to TEST?

To connect, start Rust and enter client.connect 121.80.41.68:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.

The small print

Server tags

What each one means.

Published as mp3,ptrak,$r?,v2634,^d,^k,^p,gmvanilla,cs167781,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp3
Max players 3 slots in total.
ts8
Group limit 8 to a team, which is the default the game ships with.
v2634
Protocol Your game must run the same version to join: the protocol is 2634.
cs167781
Build Build 167781 is what it runs.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code The region code field is empty.

Gameplay

^d
Combat training A training ground for aim and PvP, with loot given out.
^k
Build server Use it to design bases and practise builds.
^p
PvE There is no player fighting; the world itself is the danger.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.
^z
Modded Plugins or settings alter the game, so it is filed under Modded.

Note: 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.