RUST METRICSFlight deck · live data
Data live Servers11,681 Players34,835 Populated2,855 Fresh wipes 3 h93 Scan5 min
‹ All servers147.135.31.89:60422
Offline Full Queue Fresh wipe Wipe due No query

Forcerecon

Offline 147.135.31.89:60422 checked 44d ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,078no region published
Last wipe56d agomonthly schedule
Next wipe7d 15hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. 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 Sep21 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 timing

What wipe timing does Forcerecon follow?

From the force wipe, the next wipe of Forcerecon is an estimate. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 56 days 11 hours ago. A monthly wipe schedule is published in its tags.

Tags

How should you read the tags on Forcerecon?

These are the tags Forcerecon publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Protocol 2632: join only on the same game version; cs160556 (Build): Build 160556; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Forcerecon?

These Rust Metrics lists carry Forcerecon: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Player count

Where does Forcerecon sit in the rankings?

Ranking for Forcerecon: #15,078 on seven-day player hours, top – of all ranked servers.

What is the population on Forcerecon?

Forcerecon is not responding; status offline, last seen 44 days 19 hours ago.

Server details

Where does Forcerecon sit?

Reading: location. Forcerecon gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 147.135.31.89:60422.

What Rust version is Forcerecon on?

Reading: Forcerecon, Rust network protocol 2632 and build 160556, Linux. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Forcerecon, and is it online now?

Forcerecon reports offline. The last reading came 44 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is Forcerecon configured, and what rules are in force?

Reading the name gives no gather rate for Forcerecon. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on Forcerecon?

Check: map. Procedural, generated by the game, on Forcerecon.

Join

What do you do to join Forcerecon?

Press F1 in Rust and enter client.connect 147.135.31.89:60422. 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 mp50,ptrak,$r?,v2632,^m,gmrust,cs160556,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2632
Protocol Protocol 2632: join only on the same game version.
cs160556
Build Build 160556.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock 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.