RUST METRICSFlight deck · live data
Data live Servers11,665 Players44,308 Populated3,062 Fresh wipes 3 h99 Scan5 min
‹ All servers141.11.104.104:28015
Online Full Queue Fresh wipe Wipe due No query

[US] Foundry | Max 4 | PvPvE | Events |

Online NA 141.11.104.104:28015 checked 10m ago

quad biweekly wipes vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Wed 00:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

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

Entities

48 h range 67,905–70,306 · memory 2,241 MB
1239 ET SINCE RESTART 20:58

Uptime

20 h 58 min since its last restart, at the last reading
7-day average0peak 1
Rank#11,430top 51% · #1348 in NA
Last wipe12d agobiweekly schedule
Next wipe1d 9hThu 29 Oct, 11:09 UTC
Memory2,241MBat the last reading
REC 1

Players

AveragePeak
0123402:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040002:0011:0020:0006:0015:0000: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 22 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 51% of all ranked servers, top 72% in NA, and #535 of the quad servers (top 65%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 11:09 UTC, in 1d 9h. Its biweekly schedule tag · low confidence

usual gap7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. WPT 1Thu 29 Oct, 11:09 UTC1d 9h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 17hFW
  3. WPT 3Thu 12 Nov, 11:09 UTC15d 9h
  4. WPT 4Thu 26 Nov, 11:09 UTC29d 9h
  5. WPT 5Thu 3 Dec, 19:00 UTC36d 17hFW
  6. WPT 6Thu 10 Dec, 11:09 UTC43d 9h

The first 48 hours of its last wipes

Thu 15 OctFri 2 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, 11:09 UTC12d ago 0 – running 0
Fri 2 Oct, 02:08 UTC25d ago 0 – 13.4 days 0
Thu 1 Oct, 11:09 UTC26d ago 0 – 0.6 days 0
Wed 30 Sep, 22:10 UTC27d ago 0 – 0.5 days 0
Thu 17 Sep, 11:10 UTC40d ago 1 halved by day 1 13.5 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 [US] Foundry | Max 4 | PvPvE | Events |?

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

What wipe timing does [US] Foundry | Max 4 | PvPvE | Events | follow?

The prediction follows its tag, because too few of [US] Foundry | Max 4 | PvPvE | Events |'s wipes are on record to confirm its schedule. Thursday 29 October at 11:09 UTC is when its next wipe is due. The world it runs now was made 12 days 14 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

How should you read the tags on [US] Foundry | Max 4 | PvPvE | Events |?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts4 (Group limit): You may team up with at most 4; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): The server browser files it under North America from [US] Foundry | Max 4 | PvPvE | Events |. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show [US] Foundry | Max 4 | PvPvE | Events |?

These Rust Metrics lists carry [US] Foundry | Max 4 | PvPvE | Events |: Modded Rust servers, checked live, Rust PvE servers and North America: server readout. Check: filters. On the server list it appears under these: Region: North America; Type: Vanilla and Modded; Game mode: PvE; Server tag: Biweekly ^b, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

What position does [US] Foundry | Max 4 | PvPvE | Events | hold among Rust servers?

Ranked by seven-day player hours, [US] Foundry | Max 4 | PvPvE | Events | sits at #11,430 and #1,348 in North America, inside the top 51%. Among servers in quad, it stands at #535.

How full does [US] Foundry | Max 4 | PvPvE | Events | get?

0 of 100 slots are filled on [US] Foundry | Max 4 | PvPvE | Events | right now. Check: players over seven days. Average 0, peak 1.

Server details

Which location does [US] Foundry | Max 4 | PvPvE | Events | run from?

Reading: location. The NA tag puts [US] Foundry | Max 4 | PvPvE | Events | in North America. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 141.11.104.104:28015.

What Rust version is [US] Foundry | Max 4 | PvPvE | Events | on?

Reading: [US] Foundry | Max 4 | PvPvE | Events |, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [US] Foundry | Max 4 | PvPvE | Events |?

Reading: 213 server fps on average across the last 48 hours. It never dropped below 189. Peak entity count: 70,306. Buildings, deployables and all else included. Reading: 2,681 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is [US] Foundry | Max 4 | PvPvE | Events |, and is it online now?

Check: connection. [US] Foundry | Max 4 | PvPvE | Events | is online at this moment. Check: restart. The uptime it reports puts the last restart about 20 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What rules does [US] Foundry | Max 4 | PvPvE | Events | enforce, and what are its settings?

Check: gather rate. The name [US] Foundry | Max 4 | PvPvE | Events | does not state one. Check: group limit. 4 players, under the name quad. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. It describes itself as vanilla. The meaning given: the stock game: Facepunch's rates, kits and rules, unchanged. VAC is on. That is Valve's anti-cheat.

Which map is live on [US] Foundry | Max 4 | PvPvE | Events |?

Size 3,500 and seed 769423673: the game generates the procedural map on [US] Foundry | Max 4 | PvPvE | Events | from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to [US] Foundry | Max 4 | PvPvE | Events |?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,NA,^p,gmrust,cs168909,ts4,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts4
Group limit You may team up with at most 4.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

NA
North America The server browser files it under North America.

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.