Rust Server TrendsSeismic network · station log
Recording Stations11,699 Players51,000 Active3,284 Wipes · 3 h138 48 h

Station US-10359 · no signal

Hive staging test (shards) - dev only

Offline 194.46.57.73:28035 checked 1d ago

moddedoxide
Connect
Players now
0/ 20
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#10,359
top 47%
Last wipe
1d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station US-10359 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 20 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Mon 02:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75101:0005:0010:0014:0019:0023:00Wiped Mon 26 Oct, 12:00 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
020040060080001:0005:0010:0014:0019:0023:00Wiped Mon 26 Oct, 12:00 UTCWIPE

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 24 Oct. 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
15k10k15k20k24 Oct25 Oct26 Oct27 Oct

Top 47% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
1 daysbetween real wipes
wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 26 Oct, 12:00 UTC1d ago – – – – running 0
Sun 25 Oct, 12:00 UTC2d ago M0.3rising 2 – 1 days 0

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 · 163 on average
31/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.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 · 113 on average
55/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average
47/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
11/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
14/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Hive staging test (shards) - dev only?

Generated by the game, the map on Hive staging test (shards) - dev only is procedural and size 1,000. The name of its map is CraggyBuildBattleFieldArenaScri.

Which settings and rules apply on Hive staging test (shards) - dev only?

The name of Hive staging test (shards) - dev only gives no gather rate. It gives no group limit in its listing. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. 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.

Player counts

How many players are recorded on Hive staging test (shards) - dev only right now?

A reading taken now finds Hive staging test (shards) - dev only offline; the most recent activity was 24 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 2. The last 48 hours show their highest activity at 01:00 UTC, averaging 0 players.

How does Hive staging test (shards) - dev only rank against other Rust servers?

On player hours for the past week, Hive staging test (shards) - dev only sits at #10,359, which puts it inside the top 47% of every ranked server.

Server details

How reliably does Hive staging test (shards) - dev only stay online?

Hive staging test (shards) - dev only is down at the moment; the last recorded contact was 24 hours ago. Going by the uptime figure it reports, it restarted about 30 minutes ago. Of the 72 hours in the last 3 full days, it was up for 47, or 65% of the time. On 24 October 2026 it was recorded for the first time by Rust Server Trends.

How well does Hive staging test (shards) - dev only perform under load?

The 48-hour average is 483 server fps; 400 is the lowest observed. At its highest, it carried 1 entities: buildings, deployables and the world's other contents. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does Hive staging test (shards) - dev only run from?

No region comes from Hive staging test (shards) - dev only, though its region code is us1. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 194.46.57.73:28035.

What build of Rust does Hive staging test (shards) - dev only use?

Rust network protocol 2635 on Windows is what Hive staging test (shards) - dev only runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Hive staging test (shards) - dev only?

The recent wipes averaged a busiest count of 2 players. The peak on the most recent wipe came 3 hours after the wipe.

On what timetable does Hive staging test (shards) - dev only run its wipes?

Too few wipes of Hive staging test (shards) - dev only are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 36 hours is how long the current world has been running.

Tags

What do the server tags on Hive staging test (shards) - dev only mean?

Tags published by Hive staging test (shards) - dev only and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; ptrak (Networking): The network layer is RakNet, the game's standard; $rus1 (Region code): Region code: us1; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; dev (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; h (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; stok (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. 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 Hive staging test (shards) - dev only appear?

These Rust Server Trends lists include Hive staging test (shards) - dev only: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 3 days.

How to join

How do you connect to Hive staging test (shards) - dev only?

You can connect by pressing F1 in Rust and typing client.connect 194.46.57.73:28035 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://rustminigames.com.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$rus1,v2635,dev,h,stok,gmrust,^z,^o

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players 20 slots are available.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
ptrak
Networking The network layer is RakNet, the game's standard.
$rus1
Region code Region code: us1.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^o
Oxide A plugin framework, Oxide (uMod), runs here.

Other

dev
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.
h
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.
stok
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.

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.