Rust Data

rustdata.spaceservers104.192.227.10:28017.ipynb

Run all rust-data · live

‹ All servers

Online 104.192.227.10:28015 checked 8m ago

Chill PVE for hard workers

moddedoxidepve

Connect

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

Right now

srv.summary()
players now 0/70 # 0% full
7-day average 0 # peak 2
rank #6,501 # top 29%
last wipe 13d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75104:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510004:0013:0022:0007:0016:0002: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 17 Sep. 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 29% 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 gap14.2 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Fri 16 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 01:51 UTC13d ago 3 NaN running 1
1 Thu 1 Oct, 21:51 UTC FW27d ago 3 halved by day 5 14.2 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

6000 · seed 3343399825
Map of Chill PVE for hard workers
map
Procedural Map
size
6000
seed
3343399825
Open on RustMaps

Server

srv.info()
address
104.192.227.10:28015
region
–
max players
70
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 01:51 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
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 250 on average245/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 241 on average94/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 104 on average131/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average35/200
4[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 53 on average42/300
5TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 51 on average8/100

Quick answers

From the figures on this page.

Population

What position does Chill PVE for hard workers take in the server rankings?

Rank #6,501 on seven-day player hours for Chill PVE for hard workers, within the top 29% of all ranked servers.

What population does Chill PVE for hard workers carry?

Chill PVE for hard workers reports 0 players at this refresh, with 70 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 0 players.

About the server

What does performance look like on Chill PVE for hard workers?

Averaged over 48 hours: 70 server fps, never under 53. Entity numbers reached 216,467, and that includes buildings, deployables and the rest. The memory field tops out at 8,078 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is Chill PVE for hard workers on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Chill PVE for hard workers. The protocol has to match before you can join, and Steam does the updating.

How reliable is Chill PVE for hard workers, and is it up?

Chill PVE for hard workers reports itself online at the current refresh. The uptime it reports puts the last restart about 6 days 1 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

In which location is Chill PVE for hard workers hosted?

There is no region published for Chill PVE for hard workers. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 104.192.227.10:28015.

Map and rules

Which settings and rules does Chill PVE for hard workers run?

The name Chill PVE for hard workers carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Chill PVE for hard workers selected?

Size 6,000, seed 3343399825: the procedural map on Chill PVE for hard workers, 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 Chill PVE for hard workers wipe?

A rhythm cannot be read from the wipes of Chill PVE for hard workers 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 1 hours ago.

On Chill PVE for hard workers, what happens on wipe day?

The average peak over recent wipes is 3 players. Peak population on the latest wipe came 28 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 5 in the other cases.

Tags, lists

Which lists on Rust Data hold Chill PVE for hard workers, and which filters?

These Rust Data lists include Chill PVE for hard workers: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Chill PVE for hard workers?

The game's server browser reads these tags from Chill PVE for hard workers: gmrust (Game mode): Survival play, standard Rust; mp70 (Max players): 70 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

How can I connect to Chill PVE for hard workers?

The manual route: launch Rust, F1, then client.connect 104.192.227.10: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 mp70,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp70
Max players 70 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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,677 players 11,663 servers online