Rust Server TrendsSeismic network · station log
Recording Stations11,669 Players34,137 Active2,836 Wipes · 3 h86 48 h

Station XX-6171 · no signal

DevHev Local

Offline 109.194.35.245:28015 checked 1d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0falling
−1 players on the day
7-day average
1
peak 2
Rank
#6,171
top 28%
Last wipe
2d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-6171 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0falling−1 players
Sharpest hour
−1into Tue 18:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75107:0018:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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.

Channel 3 · rank movement

Rank

daily · 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.

Expected events

Wipe schedule

no rhythm it keeps

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

usual gap
2.9 daysbetween real wipes
on rhythm
40%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 26 Oct, 18:21 UTC2d ago M0.0rising 2 – running 1
Fri 23 Oct, 20:07 UTC5d ago M0.0rising 1 held half 2.9 days 0
Mon 5 Oct, 06:35 UTC23d ago M0.0steady 1 held half 18.6 days 1
Fri 2 Oct, 03:39 UTC27d ago M0.0steady 1 – 3.1 days 1
Tue 29 Sep, 22:16 UTC29d ago M0.0steady 2 – 2.2 days 2
Mon 28 Sep, 17:57 UTC30d ago M0.0rising 3 – 1.2 days 2

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 154 on average
26/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
130/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
35/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
11/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
1/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on DevHev Local?

DevHev Local runs a procedural map of size 2,000 with seed 166494, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on DevHev Local?

You will find no gather rate in the name of DevHev Local. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on DevHev Local?

No players are recorded on DevHev Local at this moment; it is offline, and the last sighting was 32 hours ago. The seven-day average is 1 players, with a peak of 2. Averaged over the last 48 hours, the busiest hour was 07:00 UTC at 1 players.

How does DevHev Local rank against other Rust servers?

The last seven days of player hours place DevHev Local at #6,171, in the top 28% of all ranked servers.

Server facts

How reliably does DevHev Local stay online?

As recorded now, DevHev Local is not reachable, the last contact having been 32 hours ago. Going by the uptime figure it reports, it restarted about 7 minutes ago. It was up 15% of the time across the last 7 full days: 25 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 28 September 2026.

How well does DevHev Local perform under load?

Its average server fps over the last 48 hours was 236, and it never dropped below 236. Buildings, deployables and all the rest of the world's entities brought it to a high of 14,895. Its highest memory use was 1,149 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does DevHev Local run from?

A region is not published by DevHev Local. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 109.194.35.245:28015 is the address it uses.

Which Rust version is DevHev Local running?

Rust network protocol 2635 and build 168909 on Windows is what DevHev Local runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on DevHev Local?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe. Half that peak was held until the next wipe in 100% of its recent wipes.

On what timetable does DevHev Local run its wipes?

There is no next wipe to predict at DevHev Local, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 2 days 9 hours is how long the current world has been running.

Server tags

What do the server tags on DevHev Local mean?

Tags published by DevHev Local and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does DevHev Local appear?

The Rust Server Trends lists that take in DevHev Local are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

What steps get you onto DevHev Local?

Enter client.connect 109.194.35.245:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players The server has 50 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.