RUST METRICSFlight deck · live data
Data live Servers11,726 Players49,195 Populated3,240 Fresh wipes 3 h114 Scan5 min
‹ All servers144.48.37.97:7107
Online Full Queue Fresh wipe Wipe due No query

Hard workers 3x

Online 144.48.37.97:7107 checked 7m ago

3x moddedoxide
COM 1 · connect

Server instruments

last reading Wed 22:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 105 SERVER FPS

Server fps

48 h low 91 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 47,838 ×1000

Entities

48 h range 32,788–50,760 · memory 2,277 MB
1239 ET SINCE RESTART 13:40

Uptime

13 h 40 min since its last restart, at the last reading
7-day average0peak 1
Rank#9,514top 43%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory2,277MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75101:0006:0011:0011:0016:0022:00Wiped Tue 27 Oct, 12:06 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020001:0006:0011:0011:0016:0022:00Wiped Tue 27 Oct, 12:06 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 5 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
15k10k15k20k5 Oct8 Oct11 Oct13 Oct16 Oct28 Oct

Top 43% 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 gap11.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 26 OctMon 5 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 12:06 UTC1d ago – – running 0
Mon 26 Oct, 07:02 UTC2d ago 1 – 1.2 days 0
Mon 5 Oct, 03:28 UTC23d ago 1 halved by day 1 21.1 days 1

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 happens on Hard workers 3x when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 1 when it didn't.

How often does Hard workers 3x wipe, and when?

There is no next wipe to predict: Hard workers 3x wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 36 hours ago the current world was made.

Tag meanings

How should you read the tags on Hard workers 3x?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Hard workers 3x. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Hard workers 3x appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Hard workers 3x: 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 3 days; Gather rate: 3x.

Player count

Where does Hard workers 3x sit in the rankings?

Player hours over seven days put Hard workers 3x at #9,514, in the top 43% of all ranked servers.

How full does Hard workers 3x get?

Current headcount on Hard workers 3x: 0 players, 40 slots available. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 12:00 UTC, averaging 0 players at that hour.

Operator and location

Where does Hard workers 3x sit?

Reading: location. Hard workers 3x gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 144.48.37.97:7107.

What Rust version is Hard workers 3x on?

Reading: Hard workers 3x, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on Hard workers 3x within range?

Over the last 48 hours the average was 111 server fps; the floor was 91. Peak entity count: 50,760. Buildings, deployables and all else included. Reading: 2,613 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is Hard workers 3x, and is it online now?

Reading: online. Hard workers 3x answers right now. Check: restart. The uptime it reports puts the last restart about 13 hours ago. Uptime for the last 7 full days: 30 of 168 hours, or 18%. Check: first contact. Rust Metrics logged it on 5 October 2026.

Settings and map

How is Hard workers 3x configured, and what rules are in force?

Gather rate check: 3x. That comes from the name Hard workers 3x. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Hard workers 3x?

From seed 1337, the game generates the procedural map on Hard workers 3x. Its size is 3,800. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.

Join

How can you get onto Hard workers 3x?

To join: start Rust, press F1 and type client.connect 144.48.37.97:7107. Or press Launch Rust here and Steam opens the game and connects you.

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 40 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.