Rust Data

rustdata.spaceservers167.114.157.40:41034.ipynb

Run all rust-data · live

‹ All servers

Offline 167.114.157.40:41033 checked 6d ago

_mod_retest_rust_oxide_0953ebd9

monthly wipes vanillamoddedoxide

Connect

srv = rust.server("167.114.157.40:41034")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,358 # top 69%
last wipe 6d ago # monthly schedule
next wipe 7d 15h # Thu 5 Nov, 19:00 UTC FW

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
15k10k15k20k8 Oct12 Oct16 Oct21 Oct25 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. # The force wipe · high confidence

usual gap4.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

Coming wipes

inatkind
07d 15hThu 5 Nov, 19:00 UTCFW force wipe
135d 15hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Thu 22 OctFri 16 OctTue 13 Oct
01234+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 Thu 22 Oct, 21:59 UTC6d ago 0 NaN running 0
1 Fri 16 Oct, 21:59 UTC12d ago 0 NaN 6 days 0
2 Tue 13 Oct, 10:44 UTC15d ago 0 NaN 3.5 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
167.114.157.40:41033
region
–
max players
50
group limit
8, the default
wipe schedule
monthly
last wipe
22 Oct 2026, 21:59 UTC
hostname
–
first seen
8 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average12/700
1404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average1/1000
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 78 on average34/700
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10EU · groups of 16+ · monthly · 70 on average26/1000
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10EU · groups of 16+ · monthly · 67 on average1/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10EU · groups of 16+ · monthly · 64 on average51/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does _mod_retest_rust_oxide_0953ebd9 rank?

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

How full does _mod_retest_rust_oxide_0953ebd9 run?

Offline now for _mod_retest_rust_oxide_0953ebd9, with the last sample 6 days 5 hours ago. Over the last seven days it averaged 0 players.

Server facts

What Rust version does _mod_retest_rust_oxide_0953ebd9 run?

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

How reliable is _mod_retest_rust_oxide_0953ebd9, and is it online now?

_mod_retest_rust_oxide_0953ebd9 is offline at this refresh; the last response came 6 days 5 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. Its earliest recorded date in Rust Data is 8 October 2026.

Which location does _mod_retest_rust_oxide_0953ebd9 run from?

For _mod_retest_rust_oxide_0953ebd9, 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 167.114.157.40:41033.

Map and rules

What rules and settings are recorded for _mod_retest_rust_oxide_0953ebd9?

No gather rate appears in the name: _mod_retest_rust_oxide_0953ebd9. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.

What is the map on _mod_retest_rust_oxide_0953ebd9?

The game generates its map: procedural, on _mod_retest_rust_oxide_0953ebd9.

Wipe data

When does _mod_retest_rust_oxide_0953ebd9 wipe, and how often?

Once a month _mod_retest_rust_oxide_0953ebd9 wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 6 days 5 hours ago. Its tags carry a monthly wipe schedule.

On _mod_retest_rust_oxide_0953ebd9, what happens on wipe day?

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

Tags, lists

Which lists on Rust Data hold _mod_retest_rust_oxide_0953ebd9, and which filters?

The Rust Data lists that _mod_retest_rust_oxide_0953ebd9 fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

How should you read the server tags on _mod_retest_rust_oxide_0953ebd9?

Read by the game's server browser, the tags _mod_retest_rust_oxide_0953ebd9 publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^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.

Join steps

How can I connect to _mod_retest_rust_oxide_0953ebd9?

In Rust, F1 opens the console: type client.connect 167.114.157.40:41033. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,^m,^v,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp50
Max players 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

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,864 players 11,668 servers online