Rust Data

rustdata.spaceservers109.194.35.245:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 109.194.35.245:28015 checked 1d ago

DevHev Local

moddedoxide

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75107:0018:00

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, measured since 28 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
12.5k5k7.5k10k28 Sep4 Oct10 Oct17 Oct23 Oct29 Oct

Top 28% 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 gap2.9 daysbetween real wipes
on rhythm40%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

Mon 26 OctFri 23 OctMon 5 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 18:21 UTC2d ago 2 NaN running 1
1 Fri 23 Oct, 20:07 UTC5d ago 1 held half 2.9 days 0
2 Mon 5 Oct, 06:35 UTC23d ago 1 held half 18.6 days 1
3 Fri 2 Oct, 03:39 UTC26d ago 1 NaN 3.1 days 1
4 Tue 29 Sep, 22:16 UTC29d ago 2 NaN 2.2 days 2
5 Mon 28 Sep, 17:57 UTC30d ago 3 NaN 1.2 days 2

# 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

2000 · seed 166494
Map of DevHev Local
map
Procedural Map
size
2000
seed
166494
Open on RustMaps

Server

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

Quick answers

From the figures on this page.

Population

What position does DevHev Local take in the server rankings?

Player hours over seven days put DevHev Local at #6,171, in the top 28% of the ranked set.

What population does DevHev Local carry?

Offline now for DevHev Local, with the last sample 32 hours ago. Over the last seven days it averaged 1 players and peaked at 2. Peak hour in the last 48 hours: 07:00 UTC, mean 1 players.

Server data

How smoothly does DevHev Local run?

The 48-hour average is 236 server fps, with a low of 236. The entity count peaked at 14,895, covering buildings, deployables and the rest of the world. The memory field tops out at 1,149 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does DevHev Local run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by DevHev Local. Steam updates your game for you, but the protocol must match to join.

How reliable is DevHev Local, and is it online now?

DevHev Local is offline at this refresh; the last response came 32 hours ago. Count back 7 minutes from its reported uptime to get the last restart. Uptime of 15% across the last 7 full days: 25 hours of 168. Rust Data logged it first on 28 September 2026.

Which location does DevHev Local run from?

No region is published by DevHev Local. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 109.194.35.245:28015.

Settings and map

What rules and settings are recorded for DevHev Local?

No gather rate appears in the name: DevHev Local. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.

Which map has DevHev Local selected?

DevHev Local runs a procedural map of size 2,000 with seed 166494, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does DevHev Local wipe?

Irregular wipe times on DevHev Local 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 2 days 9 hours ago.

What is wipe day on DevHev Local like?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags, lists

Which Rust Data filters and lists contain DevHev Local?

These Rust Data lists include DevHev Local: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on DevHev Local hold?

These tags are published by DevHev Local and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^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.

Connecting

How can I connect to DevHev Local?

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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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