Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-15454 · no signal

FortifiedPlacementTest

Offline 47.198.77.34:29115 checked 1d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,454
top 70%
Last wipe
2d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15454 · 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 4 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. 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
15k10k15k20k16 Nov17 Nov18 Nov19 Nov20 Nov

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
1.2 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Thu 19 NovTue 17 Nov
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 19 Nov, 00:44 UTC2d ago M0.0steady 0 – running 0
Tue 17 Nov, 20:05 UTC3d ago M0.0steady 0 – 1.2 days 0

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+ 18.11 EU · groups of 8+ · weekly · 128 on average
123/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
299/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
115/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
14/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on FortifiedPlacementTest?

No gather rate appears in the name of FortifiedPlacementTest. The group limit is 100 players. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on FortifiedPlacementTest right now?

No players are recorded on FortifiedPlacementTest at this moment; it is offline, and the last sighting was 41 hours ago. The seven-day average for this server is 0 players.

How does FortifiedPlacementTest rank against other Rust servers?

The last seven days of player hours place FortifiedPlacementTest at #15,454, in the top 70% of all ranked servers.

Operator and location

How reliably does FortifiedPlacementTest stay online?

As recorded now, FortifiedPlacementTest is not reachable, the last contact having been 41 hours ago. 14 of 96 hours in the last 4 full days were up time, 15% of the total. Its earliest appearance in the records of Rust Server Trends dates to 16 November 2026.

Which region does FortifiedPlacementTest run from?

No region is published by FortifiedPlacementTest. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 47.198.77.34:29115 is the address it uses.

Which Rust version is FortifiedPlacementTest running?

Rust network protocol 2636 and build 170545 on Windows is what FortifiedPlacementTest runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on FortifiedPlacementTest?

On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does FortifiedPlacementTest wipe, and on which days?

Too few wipes of FortifiedPlacementTest are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. 2 days 12 hours is how long the current world has been running.

Tags

What do the server tags on FortifiedPlacementTest mean?

These are the tags FortifiedPlacementTest publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp4 (Max players): The server has 4 slots; ts100 (Group limit): Teams are capped at 100 players; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170545 (Build): Game build: 170545; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does FortifiedPlacementTest appear?

The Rust Server Trends lists that take in FortifiedPlacementTest are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

What steps get you onto FortifiedPlacementTest?

To join, enter client.connect 47.198.77.34:29115 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp4,ptrak,$r?,v2636,gmrust,cs170545,ts100,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp4
Max players The server has 4 slots.
ts100
Group limit Teams are capped at 100 players.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs170545
Build Game build: 170545.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.