Rust Data

rustdata.spaceservers46.4.21.120:28021.ipynb

Run all rust-data · live

‹ All servers

Online 46.4.21.120:28020 checked 11m ago

Rust Testserver 02

moddedoxide

Connect

srv = rust.server("46.4.21.120:28021")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak –
rank #15,341 # top 69%
last wipe 12d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123415:0022:0006:0013:0022:0005:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040015:0022:0006:0013:0022:0005: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 11 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
15k10k15k20k11 Oct15 Oct18 Oct22 Oct25 Oct29 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

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 13:53 UTC12d ago 1 NaN running 0

# 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

1500 · seed 987047212
Map of Rust Testserver 02
map
Procedural Map
size
1500
seed
987047212
Open on RustMaps

Server

srv.info()
address
46.4.21.120:28020
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 19:29 UTC
hostname
–
first seen
11 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average55/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average81/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average29/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average6/1000

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Rust Testserver 02 rank?

Over the last seven days Rust Testserver 02 sits at #15,341 on player hours, in the top 69% of ranked servers.

How full does Rust Testserver 02 run?

Rust Testserver 02 reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.

Server data

How smoothly does Rust Testserver 02 run?

Averaged over 48 hours: 231 server fps, never under 160. The entity count peaked at 8,902, covering buildings, deployables and the rest of the world. A high of 887 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on Rust Testserver 02?

Version Rust network protocol 2635 and build 168909 on Linux is reported by Rust Testserver 02. The protocol has to match before you can join, and Steam does the updating.

How reliable is Rust Testserver 02, and is it up?

Online is the state at the latest refresh for Rust Testserver 02. A restart about 38 hours ago is what its reported uptime implies. Uptime of 34% across the last 7 full days: 57 hours of 168. The first row Rust Data holds for it is dated 11 October 2026.

Which location does Rust Testserver 02 run from?

There is no region published for Rust Testserver 02. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 46.4.21.120:28020 is its address.

Settings and map

What rules and settings are recorded for Rust Testserver 02?

No gather rate appears in the name: Rust Testserver 02. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has Rust Testserver 02 selected?

Rust Testserver 02 runs a procedural map of size 1,500 with seed 987047212, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does Rust Testserver 02 wipe, and on what schedule?

The record for Rust Testserver 02 holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 12 days 11 hours ago.

What is wipe day on Rust Testserver 02 like?

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

Tags, lists

Which lists on Rust Data hold Rust Testserver 02, and which filters?

On Rust Data, Rust Testserver 02 appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: 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 Rust Testserver 02?

These tags are published by Rust Testserver 02 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.

Connecting

What is the way to join Rust Testserver 02?

Enter client.connect 46.4.21.120:28020 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players Slot count: 40.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^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 33,784 players 11,611 servers online