Rust Data

rustdata.spaceservers104.128.58.197:28016.ipynb

Run all rust-data · live

‹ All servers

Online 104.128.58.197:28015 checked 8m ago

[TEST] WipeDay Test

moddedcarbon

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040000:0009:0018:0002:0011:0021: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 15 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
15k10k15k20k14 Oct17 Oct20 Oct22 Oct25 Oct28 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.

usual gap1.1 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 15 OctWed 14 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 15 Oct, 18:01 UTC13d ago 0 NaN running 0
1 Wed 14 Oct, 14:47 UTC14d ago 0 NaN 1.1 days 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 249036398
Map of [TEST] WipeDay Test
map
Procedural Map
size
1500
seed
249036398
Open on RustMaps

Server

srv.info()
address
104.128.58.197:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
15 Oct 2026, 18:01 UTC
hostname
–
first seen
14 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 · 157 on average61/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average57/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average53/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average17/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does [TEST] WipeDay Test rank?

Rank #15,344 on seven-day player hours for [TEST] WipeDay Test, within the top 69% of all ranked servers.

How full does [TEST] WipeDay Test run?

Current row: 0 players on [TEST] WipeDay Test, against 50 slots. Over the last seven days it averaged 0 players.

Server facts

How well does [TEST] WipeDay Test perform?

The 48-hour average is 239 server fps, with a low of 238. The entity count peaked at 7,826, covering buildings, deployables and the rest of the world. A high of 1,475 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does [TEST] WipeDay Test run?

Version Rust network protocol 2634 and build 167781 on Linux is reported by [TEST] WipeDay Test. Steam updates your game for you, but the protocol must match to join.

Is [TEST] WipeDay Test up, and what does its uptime show?

[TEST] WipeDay Test reports itself online at the current refresh. A restart about 4 days 14 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 14 October 2026.

Which location does [TEST] WipeDay Test run from?

For [TEST] WipeDay Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 104.128.58.197:28015.

Map and rules

What rules and settings are recorded for [TEST] WipeDay Test?

You will not find a gather rate in the string [TEST] WipeDay Test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

Which map has [TEST] WipeDay Test selected?

Size 1,500, seed 249036398: the procedural map on [TEST] WipeDay Test, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

When does [TEST] WipeDay Test wipe, and on what schedule?

A rhythm cannot be read from the wipes of [TEST] WipeDay Test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 13 days 5 hours ago.

On [TEST] WipeDay Test, what happens on wipe day?

Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Where does [TEST] WipeDay Test appear among Rust Data lists and filters?

The Rust Data lists that [TEST] WipeDay Test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on [TEST] WipeDay Test hold?

The game's server browser reads these tags from [TEST] WipeDay Test: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into [TEST] WipeDay Test?

Enter client.connect 104.128.58.197:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://wipeday.thunderdome.gg is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Recorded game build: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Plugin framework: Carbon.

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 55,890 players 11,751 servers online