RUST METRICSFlight deck · live data
Data live Servers11,643 Players57,901 Populated3,212 Fresh wipes 3 h146 Scan5 min
‹ All servers15.204.68.221:22841
Online Full Queue Fresh wipe Wipe due No query

hushs 3x/solo/duo/trio

Online 15.204.68.221:22841 checked 6m ago

3x moddedoxide
COM 1 · connect

Server instruments

last reading Fri 08:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 216 SERVER FPS

Server fps

48 h low 189 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 46,617 ×1000

Entities

48 h range 38,454–46,704 · memory 3,100 MB
1239 ET SINCE RESTART 16:26

Uptime

16 h 26 min since its last restart, at the last reading
7-day average0peak –
Rank#15,257top 69%
Last wipe8d agono schedule published
Next wipe–no rhythm it keeps
Memory3,100MBat the last reading
REC 1

Players

AveragePeak
0123410:0020:0005:0014:0023:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040010:0020:0005:0014:0023:0008:00

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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct14 Oct18 Oct22 Oct26 Oct30 Oct

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

PLAN

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 gap1 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 1

The first 48 hours of its last wipes

Thu 22 OctTue 20 OctFri 16 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 06:46 UTC8d ago 1 – running 0
Tue 20 Oct, 07:08 UTC10d ago 2 – 2 days 2
Fri 16 Oct, 08:30 UTC14d ago 2 held half 3.9 days 2
Thu 15 Oct, 07:03 UTC15d ago 2 – 1.1 days 1
Wed 14 Oct, 07:19 UTC16d ago 2 – 1 days 0
Mon 12 Oct, 07:43 UTC18d ago 1 halved by day 1 2 days 1
Sun 11 Oct, 07:04 UTC19d ago 1 – 1 days 1
Sat 10 Oct, 21:53 UTC19d ago 1 – 0.4 days 1
Sat 10 Oct, 05:18 UTC20d ago 1 – 0.7 days 0
Fri 9 Oct, 23:11 UTC20d ago 1 – 0.3 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on hushs 3x/solo/duo/trio?

The busiest point of its recent wipes drew 2 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 50% of recent wipes. When it didn't hold, by day 1 it fell below half.

What wipe timing does hushs 3x/solo/duo/trio follow?

No next wipe can be predicted for hushs 3x/solo/duo/trio, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 8 days 2 hours ago the current world was made.

Lists and filters

Which tags does hushs 3x/solo/duo/trio carry, and what do they mean?

These are the tags hushs 3x/solo/duo/trio publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does hushs 3x/solo/duo/trio appear in Rust Metrics lists and filters?

Rust Metrics lists featuring hushs 3x/solo/duo/trio: 3x Rust servers, checked live and 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 2 weeks; Gather rate: 3x.

Player count

What position does hushs 3x/solo/duo/trio hold among Rust servers?

Ranking for hushs 3x/solo/duo/trio: #15,257 on seven-day player hours, top 69% of all ranked servers.

What player count does hushs 3x/solo/duo/trio carry?

Current headcount on hushs 3x/solo/duo/trio: 0 players, 40 slots available. Seven-day reading: 0 players on average.

Operator and location

Where does hushs 3x/solo/duo/trio sit?

No region comes from hushs 3x/solo/duo/trio. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 15.204.68.221:22841.

What Rust version is hushs 3x/solo/duo/trio on?

Rust network protocol 2635 and build 168909 on Linux is the build hushs 3x/solo/duo/trio runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for hushs 3x/solo/duo/trio?

Check: fps. Average 228 server fps over the last 48 hours, low of 189. Within range. Reading: 46,704 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 3,640 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on hushs 3x/solo/duo/trio, and is it online?

Check: connection. hushs 3x/solo/duo/trio is online at this moment. By its reported uptime, the last restart was roughly 16 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 9 October 2026.

Settings and map

How is hushs 3x/solo/duo/trio configured, and what rules are in force?

The name carries the rate: 3x gather on hushs 3x/solo/duo/trio. No limit is set beyond the default. Groups take up to 8 players. 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. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is hushs 3x/solo/duo/trio on?

Size 3,000 and seed 43237: the game generates the procedural map on hushs 3x/solo/duo/trio from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto hushs 3x/solo/duo/trio?

Press F1 in Rust and enter client.connect 15.204.68.221:22841. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players The server holds 40 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter 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.