StatusLive Servers online11,681 Players34,835 Populated2,855 Wiped · 3 h93 Interval5 min Date29 OCT 2026

DWG RG-S6515Server sheetchecked 1d ago

FireRust TEST SERVER

Offline EU 162.55.236.48:29015 checked 1d ago

biweekly wipes moddedoxide
Connect
Players now 1/ 10 10% full
7-day average1peak 1
Rank#6,515top 29% · #1925 in EU
Last wipe24d agobiweekly schedule
Next wipe3d 2hSun 1 Nov, 06:20 UTC
Fig. 1

Players

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

Hourly average and peak, UTC.

Fig. 1Players on FireRust TEST SERVER
Fig. 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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct12 Oct22 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

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

wipe-day peak2players, last three wipes

Coming wipes

  1. 3d 2hSun 1 Nov, 06:20 UTC
  2. 7d 15hThu 5 Nov, 19:00 UTCFW
  3. 17d 2hSun 15 Nov, 06:20 UTC
  4. 31d 2hSun 29 Nov, 06:20 UTC
  5. 35d 15hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 06:20 UTC24d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
PRIME RUST Х5 MAX5 ДЛЯ НОВИЧКОВEU · groups of 5 · biweekly · 1 on average
0 / 200
02
Rusty Moose |EU Low|EU · groups of 6 · biweekly · 9 on average
3 / 200
03
[GER]DuKs#1 Anfängerfreundlich - PVP, low Upkeep, Raid TimesEU · groups of 5 · biweekly · 3 on average
0 / 100
04
RETRO RUST #3 Х5|MAX 5|LOOT+|CRAFT GLOBAL 22.10EU · groups of 5 · weekly · 77 on average
4 / 250
05 18 / 150
06
UA | ВИЖИВАЧ | MAIN |X2| PVP | PVEEU · groups of 6 · 2x · biweekly · 2 on average
0 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is FireRust TEST SERVER, and is it online now?

The current state of FireRust TEST SERVER is offline, with the last sighting 30 hours ago. The uptime it reports puts the last restart at about 4 hours ago. 22 of 168 hours up over the last 7 full days, which is 13% of the time. On 15 September 2026 is when Rust Graphs first saw it.

What does the recorded performance of FireRust TEST SERVER show?

Average server fps over the last 48 hours is 38; the lowest was 30. Counted at its highest: 126,237 entities, buildings, deployables and the rest of the world included. 4,214 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

In which location is FireRust TEST SERVER hosted?

In Europe FireRust TEST SERVER lists itself, tagged EU. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 162.55.236.48:29015 is its address.

What Rust version is recorded for FireRust TEST SERVER?

Rust network protocol 2635 and build 168909 on Linux: that is what FireRust TEST SERVER runs. To join, your game must be on the same protocol; Steam handles the update.

Counts

What player count is recorded on FireRust TEST SERVER?

No response from FireRust TEST SERVER; the server was last seen 30 hours ago. The seven-day mean is 1 players; the peak over the same period is 1. Averaged over the last 48 hours, the player count is highest at 16:00 UTC: 1 players.

What rank has been recorded for FireRust TEST SERVER?

FireRust TEST SERVER also measures #1,925 in Europe on the same seven-day player-hour count, at #6,515 globally and in the top 29% of ranked servers.

Wipe data

What happens on FireRust TEST SERVER on the day of a wipe?

The recent wipes averaged a busiest count of 2 players. 16 hours after the latest wipe, the crowd peaked.

What wipe schedule has been recorded for FireRust TEST SERVER?

Too few of FireRust TEST SERVER's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Sunday 1 November at 06:20 UTC is the date its next wipe is due. The current world has been in use since 24 days 21 hours ago. The tags state a wipe schedule at two-week intervals.

Rules and settings

What settings and rules apply on FireRust TEST SERVER?

The name of FireRust TEST SERVER records no gather rate. 5 players per group at most. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is FireRust TEST SERVER played?

FireRust TEST SERVER runs a procedural map of size 4,250 with seed 1471259668, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Lists and filters

Where does FireRust TEST SERVER appear among the Rust Graphs lists and filters?

These Rust Graphs lists include FireRust TEST SERVER: Europe servers, plotted and Modded Rust servers. These filters on the server list return it: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Which meaning is attached to each tag on FireRust TEST SERVER?

Tags published by FireRust TEST SERVER, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): The slot count is 10; ts5 (Group limit): The team limit is 5; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EU (Europe): In the server browser it appears under Europe. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

By what method do you join FireRust TEST SERVER?

Connect with client.connect 162.55.236.48:29015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp10
Max players The slot count is 10.
ts5
Group limit The team limit is 5.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Region

EU
Europe In the server browser it appears 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.

KeyTag string decoded