Rust Data

rustdata.spaceservers121.80.41.68:28017.ipynb

Run all rust-data · live

‹ All servers

Online 121.80.41.68:28015 checked 13m ago

TEST

moddedoxidepve

Connect

srv = rust.server("121.80.41.68:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/3 # 0% full
7-day average 0 # peak 1
rank #15,241 # top 69%
last wipe 9d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608022:0007:0016:0002:0011:0020:00

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k17 Oct19 Oct21 Oct23 Oct25 Oct27 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 18 Oct, 10:32 UTC9d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4500 · seed 823183683
Map of TEST
map
Procedural Map
size
4500
seed
823183683
Open on RustMaps

Server

srv.info()
address
121.80.41.68:28015
region
–
max players
3
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 10:32 UTC
hostname
–
first seen
17 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

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

Quick answers

From the figures on this page.

Player counts

How does TEST compare in the rankings?

Player hours over seven days put TEST at #15,241, in the top 69% of the ranked set.

How many players does TEST hold at once?

The sample now reads 0 players for TEST, out of 3 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server data

How well does TEST perform?

Averaged over 48 hours: 60 server fps, never under 58. Buildings, deployables and all else in the world took the count as high as 133,669 entities. The memory field tops out at 7,557 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is TEST on?

The build is Rust network protocol 2634 and build 167781 on Linux, run by TEST. The protocol has to match before you can join, and Steam does the updating.

Is TEST up, and what does its uptime show?

TEST reports itself online at the current refresh. Count back 9 days 9 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 17 October 2026.

In which location is TEST hosted?

For TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 121.80.41.68:28015.

Map and rules

Which settings and rules does TEST run?

No gather rate appears in the name: TEST. No custom cap; the default of 8 players per group stands. combat training is the game mode here, and practice for aim and PvP, loot given. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has TEST loaded?

The game generates the map on TEST: procedural, size 4,500, seed 823183683. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does TEST wipe, and on what schedule?

Too few wipes are on record for TEST to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 9 days 11 hours ago, and that is the one in play.

What is wipe day on TEST like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

Which Rust Data filters and lists contain TEST?

On Rust Data, TEST appears in these lists: Modded Rust servers, Rust aim training servers, Servers with build or creative tags and Rust PvE servers. It appears under these filters on the server list: 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 server tags on TEST?

Read by the game's server browser, the tags TEST publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp3 (Max players): Slot count: 3; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^d (Combat training): Practise aim and PvP; the loot is provided; ^k (Build server): Base design and practice; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to TEST?

The manual route: launch Rust, F1, then client.connect 121.80.41.68:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp3
Max players Slot count: 3.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Build number: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Gameplay

^d
Combat training Practise aim and PvP; the loot is provided.
^k
Build server Base design and practice.
^p
PvE PvE: the world is the threat, not other players.

Mods and access

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

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.

Rust Data 71,592 players 11,819 servers online