Rust Data

rustdata.spaceservers109.94.2.118:28506.ipynb

Run all rust-data · live

‹ All servers

Offline 109.94.2.118:28015 checked 1d ago

Angry Rust TEST SERVER

moddedcarbon

Connect

srv = rust.server("109.94.2.118:28506")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,269 # top 68%
last wipe 1d ago # no schedule published
next wipe – # no rhythm it keeps

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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.2 daysbetween real wipes
on rhythm29%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Wed 21 OctWed 14 OctSun 11 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 28 Oct, 07:37 UTC1d ago NaN NaN running 0
1 Wed 21 Oct, 08:57 UTC8d ago 0 NaN 6.9 days 0
2 Wed 14 Oct, 16:25 UTC15d ago 1 held half 6.7 days 1
3 Sun 11 Oct, 11:40 UTC18d ago 1 NaN 3.2 days 0
4 Thu 8 Oct, 07:06 UTC21d ago 1 NaN 3.2 days 0
5 Fri 2 Oct, 16:41 UTC27d ago 1 NaN 5.6 days 0
6 Thu 1 Oct, 06:41 UTC28d ago 1 NaN 1.4 days 0
7 Wed 30 Sep, 09:03 UTC29d ago 1 NaN 0.9 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
109.94.2.118:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
28 Oct 2026, 07:37 UTC
hostname
–
first seen
13 Sep 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 average85/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average150/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average58/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average153/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average346/350

Quick answers

From the figures on this page.

Population data

How does Angry Rust TEST SERVER compare in the rankings?

Rank #15,269 on seven-day player hours for Angry Rust TEST SERVER, within the top 68% of all ranked servers.

How full does Angry Rust TEST SERVER run?

Offline now for Angry Rust TEST SERVER, with the last sample 36 hours ago. Over the last seven days it averaged 0 players.

Server facts

What Rust version does Angry Rust TEST SERVER run?

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

Is Angry Rust TEST SERVER up, and what does its uptime show?

Angry Rust TEST SERVER is offline at this refresh; the last response came 36 hours ago. Over the last 7 full days the hours up number 1 of 168, 1%. Rust Data logged it first on 13 September 2026.

Where does Angry Rust TEST SERVER sit?

No region is published by Angry Rust TEST SERVER. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 109.94.2.118:28015 is its address.

Rules, settings, map

Which rules apply on Angry Rust TEST SERVER, and what settings?

You will not find a gather rate in the string Angry Rust TEST SERVER. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. 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.

What is the map on Angry Rust TEST SERVER?

A procedural map runs on Angry Rust TEST SERVER, generated by the game.

Wipe data

When does Angry Rust TEST SERVER wipe, and on what schedule?

Irregular wipe times on Angry Rust TEST SERVER leave no next wipe to forecast. 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 36 hours ago.

On Angry Rust TEST SERVER, what happens on wipe day?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold Angry Rust TEST SERVER, and which filters?

These Rust Data lists include Angry Rust TEST SERVER: 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 3 days.

How should you read the server tags on Angry Rust TEST SERVER?

These tags are published by Angry Rust TEST SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Angry Rust TEST SERVER?

The manual route: launch Rust, F1, then client.connect 109.94.2.118: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 mp50,ptrak,$r?,v2634,gmrust,cs166586,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players Slot count: 50.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166586
Build Recorded game build: 166586.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Runs on Carbon for plugins.

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 100,368 players 11,855 servers online