Rust Data

rustdata.spaceservers2.27.44.192:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 2.27.44.192:28015 checked 15d ago

WARZONE #3 [X5 | TEST SERVER] Wipe 19.05

5x trio weekly wipes moddedoxide

Connect

srv = rust.server("2.27.44.192:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 30/100 # 30% full
7-day average 0 # peak –
rank #5,921 # top 27%
last wipe 25d ago # weekly schedule
next wipe 2d 9h # Fri 30 Oct, 11:23 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. 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
12k4k6k8k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 27% of all ranked servers, and #370 of the trio servers (top 59%). Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Next wipe Friday 30 October, 11:23 UTC, in 2d 9h. # Weekly: 7 days after its last wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
2.27.44.192:28015
region
–
max players
100
group limit
trio
wipe schedule
weekly
last wipe
2 Oct 2026, 11:23 UTC
hostname
–
first seen
12 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0WARBANDITS.GG EU 5X |Solo/Duo/Trio|Loot+|TP|Kits|x5 JUST WIPEDEU · trio · 5x · weekly · 8 on average7/100
1RustSpain.com | EU España x5 (Wipe 26.10 10/26) [Solo/Duo/TrioEU · trio · 5x · weekly · 4 on average4/50
2RustForNoobs.com | 5x | Solo Duo Trio |x5 EU | No BPs | KitsEU · trio · 5x · weekly · 3 on average1/100
3EU Vex.gg 5x Solo/Duo/Trio|Shared BPs|Kits|Shop|max 3 Best 10x5EU · trio · 5x · weekly · 3 on average2/200
4[LATAM] RusticoARG #1 — X5 • MAX 3 — WIPE 26/10SA · trio · 5x · weekly · 3 on average3/30
5RustForNoobs.com | 5x | Solo Duo Trio |x5 US | No BPs | KitsNA · trio · 5x · weekly · 3 on average0/100

Quick answers

From the figures on this page.

Population

What position does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 take in the server rankings?

Over the last seven days WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 sits at #5,921 on player hours, in the top 27% of ranked servers. Its position in the trio group is #370.

How full does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 run?

WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 returns no live count at this refresh, having last been seen 15 days 7 hours ago.

Server data

What Rust version does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 run?

The build is Rust network protocol 2634 and build 167584 on Windows, run by WARZONE #3 [X5 | TEST SERVER] Wipe 19.05. Joining needs the same protocol on your game; Steam handles the update.

How reliable is WARZONE #3 [X5 | TEST SERVER] Wipe 19.05, and is it up?

The latest sample has WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 offline, with a last sighting 15 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 12 October 2026.

Which location does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 run from?

There is no region published for WARZONE #3 [X5 | TEST SERVER] Wipe 19.05. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 2.27.44.192:28015.

Map and rules

What rules and settings are recorded for WARZONE #3 [X5 | TEST SERVER] Wipe 19.05?

Gather sits at 5x, read from the server's own name: WARZONE #3 [X5 | TEST SERVER] Wipe 19.05. trio sets the cap: 3 players per group. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 selected?

The game generates its map: procedural, on WARZONE #3 [X5 | TEST SERVER] Wipe 19.05.

Wipes and dates

On what schedule does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 wipe?

The next wipe for WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 is an estimate, drawn from weekly: 7 days after its last wipe. Friday 30 October at 11:23 UTC is when the next wipe is due. This world was created 25 days 14 hours ago. The tags list wipes as weekly.

Tags, lists

Where does WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 appear among Rust Data lists and filters?

On Rust Data, WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 appears in these lists: Modded Rust servers, Rust servers filtered by gather rate: 5x and Trio Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Gather rate: 5x; Players now: At least 10.

Which meanings do the tags on WARZONE #3 [X5 | TEST SERVER] Wipe 19.05 hold?

The game's server browser reads these tags from WARZONE #3 [X5 | TEST SERVER] Wipe 19.05: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts3 (Group limit): No team may exceed 3; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; rustmaps (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into WARZONE #3 [X5 | TEST SERVER] Wipe 19.05?

The manual route: launch Rust, F1, then client.connect 2.27.44.192: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 mp100,ptrak,$r?,v2634,^w,gmrust,cs167584,ts3,^o^z,rustmaps,modded

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players 100 slots in total.
ts3
Group limit No team may exceed 3.
v2634
Protocol To join, your game must run protocol 2634.
cs167584
Build Build number: 167584.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Wipes run weekly.

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.
modded
Modded Plugins or settings alter the game, so it sits under Modded.

Other

rustmaps
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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 45,616 players 11,643 servers online