RUST METRICSFlight deck · live data
Data live Servers11,644 Players43,541 Populated3,049 Fresh wipes 3 h97 Scan5 min
‹ All servers148.251.227.74:28015
Online Full Queue Fresh wipe Wipe due No query

Histers.com | 2x Quad | Bi-Weekly | Vanilla+

Online 148.251.227.74:28015 checked 11m ago

2x quad moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 07:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

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

Server fps

48 h low 116 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 87,224 ×1000

Entities

48 h range 86,915–89,282 · memory 4,960 MB
1239 ET SINCE RESTART 10D 18H

Uptime

10 days 18 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,338top 69%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory4,960MBat the last reading
REC 1

Players

AveragePeak
0123409:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020009:0018:0003:0012:0022:0007: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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep4 Oct10 Oct17 Oct23 Oct29 Oct

Top 69% of all ranked servers, and #625 of the quad servers (top 75%). Ranked on player hours over the last seven days.

PLAN

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 gap13.9 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 15 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 19:06 UTC13d ago 0 – running 0
Thu 1 Oct, 20:38 UTC FW27d ago 0 – 13.9 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

Reset cycle

What should you expect from wipe day on Histers.com | 2x Quad | Bi-Weekly | Vanilla+?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ follow?

To tell the rhythm of Histers.com | 2x Quad | Bi-Weekly | Vanilla+, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 13 days 13 hours ago.

Tag meanings

Which tags does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp200 (Max players): 200 slots in total; ts4 (Group limit): Team cap: 4; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon from Histers.com | 2x Quad | Bi-Weekly | Vanilla+. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Histers.com | 2x Quad | Bi-Weekly | Vanilla+: 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Quad; Last wipe: In the last 2 weeks; Gather rate: 2x.

Population

What position does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ hold among Rust servers?

Ranking for Histers.com | 2x Quad | Bi-Weekly | Vanilla+: #15,338 on seven-day player hours, top 69% of all ranked servers. Among servers in quad, it stands at #625.

What player count does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ carry?

Current headcount on Histers.com | 2x Quad | Bi-Weekly | Vanilla+: 0 players, 200 slots available. Check: player average. 0 over the last seven days.

Operator and location

Where does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ sit?

No region comes from Histers.com | 2x Quad | Bi-Weekly | Vanilla+. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 148.251.227.74:28015.

What Rust version is Histers.com | 2x Quad | Bi-Weekly | Vanilla+ on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by Histers.com | 2x Quad | Bi-Weekly | Vanilla+. Check: protocol. To join, your game must match; Steam handles the update.

How does Histers.com | 2x Quad | Bi-Weekly | Vanilla+ perform?

Check: fps. Average 146 server fps over the last 48 hours, low of 116. Within range. Check: entities. The peak was 89,282, counting buildings, deployables and the rest of the world. Reading: 5,481 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is Histers.com | 2x Quad | Bi-Weekly | Vanilla+, and is it online now?

Reading: online. Histers.com | 2x Quad | Bi-Weekly | Vanilla+ answers right now. Reading: uptime. About 10 days 18 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 28 September 2026.

Map and rules

How is Histers.com | 2x Quad | Bi-Weekly | Vanilla+ configured, and what rules are in force?

Gather rate check: 2x. That comes from the name Histers.com | 2x Quad | Bi-Weekly | Vanilla+. The group cap is 4 players, read as quad. Mode check gives survival; 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. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Histers.com | 2x Quad | Bi-Weekly | Vanilla+?

From seed 89124, the game generates the procedural map on Histers.com | 2x Quad | Bi-Weekly | Vanilla+. Its size is 3,900. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto Histers.com | 2x Quad | Bi-Weekly | Vanilla+?

Check: join. Open Rust, press F1, then enter client.connect 148.251.227.74:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2633,gmrust,cs165217,ts4,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp200
Max players 200 slots in total.
ts4
Group limit Team cap: 4.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

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.