Rust Data LabData lab · live
Live readings Servers11,908 Players102,404 Populated3,970 Fresh wipes · 3h409 Sampled every 5 min

Element card · group Modded · atomic number 2,058, its rank

(US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP

Online NA · us5 91.229.114.45:28135 checked 10m ago

2x biweekly wipes moddedcarbon
Join the experiment
Atomic mass · players now 1/ 100 1% full Room to join
7-day average2peak 8
Rank · atomic number#2,058top 9% · #326 in NA
Last wipe13d agobiweekly schedule
Next wipe12mThu 29 Oct, 18:03 UTC
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608018:0003:0012:0022:0007:0016: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 9% of all ranked servers, top 18% in NA. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 18:03 UTC, in 12m. Its biweekly schedule tag · low confidence

usual gap7 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak5players, last three wipes
crowd held67%else halves by day 7

Coming wipes

  1. 12mThu 29 Oct, 18:03 UTC
  2. 7d 1hThu 5 Nov, 19:00 UTCFW
  3. 14d 0hThu 12 Nov, 18:03 UTC
  4. 28d 0hThu 26 Nov, 18:03 UTC
  5. 35d 1hThu 3 Dec, 19:00 UTCFW
  6. 42d 0hThu 10 Dec, 18:03 UTC

The first 48 hours of its last wipes

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

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 18:03 UTC13d ago 7 – running 1
Fri 9 Oct, 10:40 UTC20d ago 5 held half 6.3 days 1
Thu 1 Oct, 18:23 UTC FW27d ago 4 held half 7.7 days 0
Thu 17 Sep, 20:37 UTC41d ago 5 halved by day 7 13.9 days 2
Wed 16 Sep, 22:05 UTC42d ago 4 – 0.9 days 2

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
  1. 1 At Atlas - US 2X … 15
    Atlas - US 2X Medium | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · biweekly · 10 on average 15/ 100
  2. 2 Bi [US] Big Tuna … 3
    [US] Big Tuna 2x Vanilla+ | Max 8 | Just Wiped! NA · groups of 8+ · 2x · biweekly · 3 on average 3/ 75
  3. 3 At Atlas - US 2X … 152
    Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 378 on average 152/ 200
  4. 4 Us US Limitless 2… 83
    US Limitless 2x Monthly Main | No BP Wipes | x2 NA · groups of 12+ · 2x · monthly · 157 on average 83/ 200
  5. 5 Ho HollowServers.… 143
    HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 129 on average 143/ 150
  6. 6 Ho HollowServers.… 35
    HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 121 on average 35/ 100

Quick answers

from the figures on this page

Server setup

What map is in play on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

The map on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP is procedural at size 4,250 with seed 1337, made by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map. The name of the map is: Custom Map.

What settings and rules apply on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

(US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP carries a 2x gather rate, as its name states. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. Raids and player fights are part of play here. Plugins or settings change the game, so the browser lists it under Modded. Carbon plugins are running on it. The VAC anti-cheat from Valve is enabled.

Server facts

What region hosts (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

The NA tag puts (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP in North America, and its region code is us5. Rust Data Lab shows a server's stated location, not a verified position of the machine. You will find it at 91.229.114.45:28135.

Which Rust version is (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP on?

Rust network protocol 2635 and build 168909 on Linux is what (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP uses. The protocol must match for you to join; Steam will update your game.

Does (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP stay up, and how reliable is its uptime?

(US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP is live as of now. The uptime it reports suggests it restarted roughly 10 hours ago. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. On 13 September 2026, Rust Data Lab saw it for the first time.

How well does (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP perform?

The last 48 hours show an average of 53 server fps and a minimum of 7. Buildings, deployables and everything else in the world added up to as many as 86,192 entities. Up to 5,170 MB of memory was used. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe schedule

What is the wiping pattern on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

The prediction for (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP follows its tag, as too few wipes are on record to confirm the schedule. On Thursday 29 October at 18:03 UTC the next wipe falls due. Counting back, the current world began 13 days 23 hours ago. Its tags list a wipe schedule of one wipe every two weeks.

On (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP, what happens when wipe day arrives?

Recent wipes on average reached 5 players at their busiest. The latest wipe's peak fell 43 hours after it began. Above half the peak until the next wipe: that held in 67% of its recent wipes. In the other cases, half the peak was lost by day 7.

Lists and tags

Which meanings sit behind the tags on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 is the slot count; ts8 (Group limit): 8 per team, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $rus5 (Region code): Its region code reads us5; ^b (Biweekly): The map wipes on a two-week cycle; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; ^y (Carbon): The plugin framework here is Carbon; NA (North America): North America is where the browser lists this server: that is the tag list (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP appear in?

You will find (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP on the following Rust Data Lab lists: 2x gather rate servers, Modded Rust servers, measured and North American Rust servers: the sample. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.

Population

How does (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP compare with other servers in the rankings?

(US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP is #2,058 on seven-day player hours, #326 in North America, and in the top 9% of all ranked servers.

What does the current player count on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP tell you?

Of 100 slots, 1 are taken on (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP right now. The week's figures average 2 players and top out at 8. Peak time in the past 48 hours: 03:00 UTC, when the average was 3 players.

How to join

How can you connect to (US) HELL FORGE 2X | Solo/Duo/Trio | BIWEEKLY | CHILL PVP?

Open the console with F1 in Rust and type client.connect 91.229.114.45:28135. The Launch Rust button on this page does the same job through Steam. For more, visit https://discord.com/invite/4K9Y7EWrba.

Server tags

what each one means

Published as mp100,ptrak,$rus5,v2635,^z,^y,^b,NA,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players 100 is the slot count.
ts8
Group limit 8 per team, the default the game ships with.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$rus5
Region code Its region code reads us5.

Wipe schedule

^b
Biweekly The map wipes on a two-week cycle.

Mods and access

^z
Modded You will find it under Modded: the game is altered by plugins or settings.
^y
Carbon The plugin framework here is Carbon.

Region

NA
North America North America is where the browser lists this server.

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.