Rust Data

rustdata.spaceservers114.16.196.8:28017.ipynb

Run all rust-data · live

‹ All servers

Online 114.16.196.8:28015 checked 8m ago

MURAKUMA_Rust

monthly wipes moddedcarbon

Connect

srv = rust.server("114.16.196.8:28017")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040022:0007:0016:0000:0009:0019: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 2 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
15k10k15k20k2 Oct7 Oct12 Oct18 Oct23 Oct28 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 21h. # The force wipe · high confidence

wipe-day peak3players, last three wipes

Coming wipes

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

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 3, 23 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 12:06 UTC26d ago 3 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

5000 · seed 1
Map of MURAKUMA_Rust
map
Procedural Map
size
5000
seed
1
Open on RustMaps

Server

srv.info()
address
114.16.196.8:28015
region
–
max players
100
group limit
8, the default
wipe schedule
monthly
last wipe
2 Oct 2026, 12:52 UTC
hostname
–
first seen
2 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 · 91 on average102/700
1404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average29/1000
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 75 on average233/700
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10EU · groups of 16+ · monthly · 68 on average136/1000
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10EU · groups of 16+ · monthly · 67 on average8/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10EU · groups of 16+ · monthly · 59 on average368/1000

Quick answers

From the figures on this page.

Player counts

What position does MURAKUMA_Rust take in the server rankings?

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

How full does MURAKUMA_Rust run?

MURAKUMA_Rust reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.

About the server

How smoothly does MURAKUMA_Rust run?

Averaged over 48 hours: 190 server fps, never under 139. The entity count peaked at 149,703, covering buildings, deployables and the rest of the world. Memory peaked at 3,622 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is MURAKUMA_Rust on?

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

Is MURAKUMA_Rust up, and what does its uptime show?

MURAKUMA_Rust reports itself online at the current refresh. A restart about 7 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 2 October 2026.

Where does MURAKUMA_Rust sit?

For MURAKUMA_Rust, 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 114.16.196.8:28015.

Settings and map

Which rules apply on MURAKUMA_Rust, and what settings?

No gather rate appears in the name: MURAKUMA_Rust. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.

Which map has MURAKUMA_Rust selected?

MURAKUMA_Rust runs a procedural map of size 5,000 with seed 1, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

On what schedule does MURAKUMA_Rust wipe?

The only wipe MURAKUMA_Rust takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 26 days 8 hours ago. A monthly wipe schedule is published in its tags.

What is wipe day on MURAKUMA_Rust like?

The average peak over recent wipes is 3 players. 23 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Which Rust Data filters and lists contain MURAKUMA_Rust?

On Rust Data, MURAKUMA_Rust appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.

How should you read the server tags on MURAKUMA_Rust?

These tags are published by MURAKUMA_Rust and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; 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; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^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.

Connecting

How can I connect to MURAKUMA_Rust?

In Rust, F1 opens the console: type client.connect 114.16.196.8:28015. 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 mp100,ptrak,$r?,v2634,^z,^y,^m,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit Team limit of 8, as shipped by default.
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.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^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 75,437 players 11,810 servers online