RUST METRICSFlight deck · live data
Data live Servers11,618 Players39,799 Populated2,961 Fresh wipes 3 h88 Scan5 min
‹ All servers162.55.236.48:29015
Offline Full Queue Fresh wipe Wipe due No query

FireRust TEST SERVER

Offline EU 162.55.236.48:29015 checked 1d ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Tue 20:00 UTC
0 2 5 8 10 PAX 1 /10

Players now

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

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 112,521 ×1000

Entities

48 h range 112,521–126,237 · memory 4,208 MB
1239 ET SINCE RESTART 04:34

Uptime

4 h 34 min since its last restart, at the last reading
7-day average1peak 1
Rank#6,630top 30% · #1938 in EU
Last wipe25d agobiweekly schedule
Next wipe2d 22hSun 1 Nov, 06:20 UTC
Memory4,208MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75115:0016:0017:0018:0019:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304015:0016:0017:0018:0019:0020: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 18 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 Sep27 Sep4 Oct12 Oct22 Oct29 Oct

Top 30% of all ranked servers, top 66% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Sunday 1 November, 06:20 UTC, in 2d 22h. Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

  1. WPT 1Sun 1 Nov, 06:20 UTC2d 22h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 11hFW
  3. WPT 3Sun 15 Nov, 06:20 UTC16d 22h
  4. WPT 4Sun 29 Nov, 06:20 UTC30d 22h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 11hFW
  6. WPT 6Sun 13 Dec, 06:20 UTC44d 22h

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 06:20 UTC25d ago 2 – running 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

Wipe schedule

What should you expect from wipe day on FireRust TEST SERVER?

The busiest point of its recent wipes drew 2 players on average. 16 hours after the wipe, the crowd peaked on the latest wipe.

How often does FireRust TEST SERVER wipe, and when?

The prediction follows its tag, because too few of FireRust TEST SERVER's wipes are on record to confirm its schedule. Due on Sunday 1 November at 06:20 UTC is its next wipe. The world in play was created 25 days 1 hours ago. The tags carry an every-two-weeks wipe schedule.

Lists and filters

How should you read the tags on FireRust TEST SERVER?

These are the tags FireRust TEST SERVER publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts5 (Group limit): You may team up with at most 5; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; EU (Europe): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show FireRust TEST SERVER?

On Rust Metrics, FireRust TEST SERVER sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Population

What position does FireRust TEST SERVER hold among Rust servers?

Player hours over the last seven days put FireRust TEST SERVER at #6,630, #1,938 in Europe, in the top 30% of all ranked servers.

What is the population on FireRust TEST SERVER?

FireRust TEST SERVER is not responding; status offline, last seen 35 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 16:00 UTC, 1 players on average.

Server details

Which location does FireRust TEST SERVER run from?

FireRust TEST SERVER gives Europe as its location, with the EU tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 162.55.236.48:29015.

What Rust version is FireRust TEST SERVER on?

Reading: FireRust TEST SERVER, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does FireRust TEST SERVER perform?

Reading: 38 server fps on average across the last 48 hours. It never dropped below 30. Reading: 126,237 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,214 MB. What players call lag comes from low fps and an entity count on the rise.

Is FireRust TEST SERVER up, and how often does it stay up?

Reading: offline. FireRust TEST SERVER last answered 35 hours ago. Reading: uptime. About 4 hours ago it restarted, on its own count. Uptime for the last 7 full days: 22 of 168 hours, or 13%. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Rules and settings

How is FireRust TEST SERVER configured, and what rules are in force?

No gather rate appears in the name: FireRust TEST SERVER. Check: group limit. Up to 5 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is FireRust TEST SERVER on?

From seed 1471259668, the game generates the procedural map on FireRust TEST SERVER. Its size is 4,250. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join FireRust TEST SERVER?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,^b,EU,gmrust,cs168909,ts5,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts5
Group limit You may team up with at most 5.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

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

Region

EU
Europe The server browser files it under Europe.

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.