Rust Server TrendsSeismic network · station log
Recording Stations11,837 Players92,814 Active3,817 Wipes · 3 h495 48 h

Station EU-15496 · no signal

RTS FIRE

Offline EU 37.230.210.24:26000 checked 42d ago

weekly wipes vanillamoddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,496
#2546 in EU
Last wipe
43d ago
weekly schedule
Next wipe
5d 19h
Wed 4 Nov, 16:29 UTC
Seismic record · station EU-15496 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep
Expected events

Wipe schedule

Next wipe Wednesday 4 November, 16:29 UTC, in 5d 19h. Weekly: 7 days after its last wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
129/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 119 on average
119/ 225
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
349/ 350
[EU] Willjum's Solo Only | Thursday Wipes EU · groups of 8+ · weekly · 25 on average
97/ 175
TRAVELER SOLO [MAX 1] Wipe 26.10 EU · no group limit · weekly · 24 on average
23/ 100
35+ВЗРОСЛЫЙ RUSTx2 MAIN EU · groups of 128+ · weekly · 9 on average
5/ 125
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RTS FIRE?

Generated by the game, the map on RTS FIRE is procedural, size 3,600 with seed 1337. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on RTS FIRE?

The name of RTS FIRE gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on RTS FIRE right now?

A reading taken now finds RTS FIRE offline; the most recent activity was 42 days 5 hours ago.

How does RTS FIRE rank against other Rust servers?

RTS FIRE is #2,546 in Europe and #15,496 worldwide on the past week's player hours, within the top – of ranked servers.

Server facts

How reliably does RTS FIRE stay online?

No contact with RTS FIRE right now, and the last recorded contact was 42 days 5 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 16 September 2026.

Which region does RTS FIRE run from?

With its EU tag, RTS FIRE lists itself in Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 37.230.210.24:26000.

Which Rust version is RTS FIRE running?

Rust network protocol 2633 and build 163794 on Linux is what RTS FIRE runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

How often does RTS FIRE wipe, and on which days?

An estimate from weekly: 7 days after its last wipe gives RTS FIRE's next wipe. The date of its next wipe is Wednesday 4 November at 16:29 UTC. The present world dates from 43 days 4 hours. The tags it publishes carry a weekly wipe schedule.

Server tags

What do the server tags on RTS FIRE mean?

Tags published by RTS FIRE and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes happen weekly; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): In the server browser it appears under Europe. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does RTS FIRE appear?

You will find RTS FIRE on the following Rust Server Trends lists: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.

How to join

What steps get you onto RTS FIRE?

Enter client.connect 37.230.210.24:26000 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. https://hosting.alkad.org/ is where its website lives.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^w,^v,EU,gmvanilla,cs163794,ts8,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp100
Max players 100 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs163794
Build The game build is 163794.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Wipe schedule

^w
Weekly Wipes happen weekly.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.