DevHev Local
Offline 109.194.35.245:28015 checked 1d ago
Server instruments
last reading Tue 18:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 236 · below 20 is lag, below 10 is badEntities
48 h range 14,895–14,895 · memory 1,149 MBUptime
0 h 7 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 28% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 18:21 UTC2d ago | 2 | – | running | 1 |
| Fri 23 Oct, 20:07 UTC5d ago | 1 | held half | 2.9 days | 0 |
| Mon 5 Oct, 06:35 UTC23d ago | 1 | held half | 18.6 days | 1 |
| Fri 2 Oct, 03:39 UTC27d ago | 1 | – | 3.1 days | 1 |
| Tue 29 Sep, 22:16 UTC29d ago | 2 | – | 2.2 days | 2 |
| Mon 28 Sep, 17:57 UTC30d ago | 3 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 26/500
- 130/100
- 35/225
- 11/700
- 3/200
- 1/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on DevHev Local?
At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does DevHev Local wipe, and when?
There is no next wipe to predict: DevHev Local wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 2 days 9 hours ago the current world was made.
Tag meanings
Which tags does DevHev Local carry, and what do they mean?
Tags published by DevHev Local, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does DevHev Local appear in Rust Metrics lists and filters?
On Rust Metrics, DevHev Local sits in these lists: Modded Rust servers, checked live. These filters bring it up 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.
Population
Where does DevHev Local sit in the rankings?
Player hours over seven days put DevHev Local at #6,171, in the top 28% of all ranked servers.
What player count does DevHev Local carry?
DevHev Local is not responding; status offline, last seen 32 hours ago. Seven-day check: 1 players on average. Peak reading: 2. Check: 48-hour peak. 07:00 UTC, 1 players on average.
Server
Where does DevHev Local sit?
No region tag on DevHev Local. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 109.194.35.245:28015.
What Rust version is DevHev Local on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by DevHev Local. To get in, your game needs the same protocol; Steam applies the update.
How does DevHev Local perform?
Reading: 236 server fps on average across the last 48 hours. It never dropped below 236. Peak entity count: 14,895. Buildings, deployables and all else included. Check: memory. Peak use was 1,149 MB. Expect lag when fps falls and entities climb.
What is the uptime on DevHev Local, and is it online?
Check: connection. DevHev Local is offline at this moment. Last contact was 32 hours ago. Check: restart. The uptime it reports puts the last restart about 7 minutes ago. Uptime for the last 7 full days: 25 of 168 hours, or 15%. The first sighting on Rust Metrics was 28 September 2026.
Settings and map
What rules does DevHev Local enforce, and what are its settings?
No gather rate appears in the name: DevHev Local. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is DevHev Local on?
Check: map. Procedural, size 2,000, seed 166494, generated by the game on DevHev Local. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
What do you do to join DevHev Local?
Press F1 in Rust and enter client.connect 109.194.35.245:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.