Rust Server Analytics 54,186 players11,674 servers
All servers
Drill-through Server detail

Hive staging test (shards) - dev only

Offline 194.46.57.73:28035 checked 1d ago

Drill-through
FilterServeris Hive staging test (shards) - dev only
Attributes
moddedoxide
Last refreshed
Players now 0/ 20
7-day average 0 peak 2
Rank #10,371 top 47%
Last wipe 1d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeakWipe
0123411:0013:0016:0018:0021:0023:00Wiped Mon 26 Oct, 12:00 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
020040060080011:0013:0016:0018:0021: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Oct25 Oct26 Oct27 Oct28 Oct

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

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 gap1 daysbetween real wipes
wipe-day peak2players, 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 12:00 UTC1d ago – – running 0
Sun 25 Oct, 12:00 UTC2d ago 2 – 1 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 155 on average 158 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 135 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 115 on average 184 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average 110 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 9 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 47 / 1000

Quick answers

from the figures on this page

Wipe data

When does Hive staging test (shards) - dev only wipe?

The rhythm of Hive staging test (shards) - dev only cannot yet be told: too few of its wipes are on record. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 46 hours ago.

Wipe day on Hive staging test (shards) - dev only: what should you expect?

The average busiest count over recent wipes is 2 players. Peak population for the latest wipe came 3 hours after it began.

Server details

In which region does Hive staging test (shards) - dev only sit?

A region is not published by Hive staging test (shards) - dev only; its region code reads us1. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 194.46.57.73:28035.

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

The platform is Windows, with Rust network protocol 2635 running on Hive staging test (shards) - dev only. Your game must match the protocol to join, and Steam applies that update.

What uptime does Hive staging test (shards) - dev only show, and is it up?

Offline at this refresh: Hive staging test (shards) - dev only, last seen 34 hours ago. About 30 minutes ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (3) was 65%, or 47 of 72 hours. 24 October 2026 is when Rust Server Analytics first recorded it.

Is performance on Hive staging test (shards) - dev only stable?

Server fps averaged 477 over the last 48 hours, with a floor of 400. Entity count reached 1, covering buildings, deployables and the rest of the world. Players experience lag as low fps combined with a rising entity count.

Tags

How should the tags on Hive staging test (shards) - dev only be read?

The game's server browser reads the tags Hive staging test (shards) - dev only publishes: gmrust (Game mode): Rust survival, standard ruleset; mp20 (Max players): Capacity of 20 slots; v2635 (Protocol): To join, your game version must match protocol 2635; ptrak (Networking): RakNet is the network layer, the game's standard one; $rus1 (Region code): us1 is the region code on record; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^o (Oxide): The Oxide (uMod) plugin framework is installed; dev (Custom tag): Outside the standard tag set, added by the owner or a plugin; h (Custom tag): Outside the standard tag set, added by the owner or a plugin; stok (Custom tag): Outside the standard tag set, added by the owner or a plugin. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does Hive staging test (shards) - dev only appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists Hive staging test (shards) - dev only fits are: Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 3 days.

Population

What position does Hive staging test (shards) - dev only hold in the server rankings?

The seven-day player-hours rank for Hive staging test (shards) - dev only is #10,371, inside the top 47% of all ranked servers.

How many players does Hive staging test (shards) - dev only carry?

The last sighting of Hive staging test (shards) - dev only was 34 hours ago; it is offline at this refresh. Averaging 0 players across seven days, the server reached a peak of 2.

Settings

What are the settings on Hive staging test (shards) - dev only, and its rules?

No gather rate is given in the name of Hive staging test (shards) - dev only. Group limit: not published. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.

What is the map for Hive staging test (shards) - dev only?

Hive staging test (shards) - dev only uses a procedural map of size 1,000, generated by the game. The map is called CraggyBuildBattleFieldArenaScri.

How to join

What is the way onto Hive staging test (shards) - dev only?

In the Rust console (F1), enter client.connect 194.46.57.73:28035. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://rustminigames.com is its website.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard ruleset.
mp20
Max players Capacity of 20 slots.
v2635
Protocol To join, your game version must match protocol 2635.
ptrak
Networking RakNet is the network layer, the game's standard one.
$rus1
Region code us1 is the region code on record.

Mods and access

^z
Modded Plugins or settings change the game, so it sits under Modded.
^o
Oxide The Oxide (uMod) plugin framework is installed.

Other

dev
Custom tag Outside the standard tag set, added by the owner or a plugin.
h
Custom tag Outside the standard tag set, added by the owner or a plugin.
stok
Custom tag Outside the standard tag set, added 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.