Rust Server TrendsSeismic network · station log
Recording Stations11,801 Players69,381 Active3,608 Wipes · 3 h186 48 h

Station XX-3953 · recording

RustServer_5018

Online 133.88.106.75:28015 checked 14m ago

Connect
Players now
1/ 50
2% full
Motion · 24 h
M0.0rising
+0 players on the day
7-day average
1
peak 6
Rank
#3,953
top 18%
Last wipe
5d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-3953 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 50 slots
Motion · 24 h
M0.0rising+0 players
Sharpest hour
−2into Tue 15:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123414:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020014:0023:0008:0016:0002:0011: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 24 Oct. 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
12k4k6k8k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct

Top 18% 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.

wipe-day peak
6players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 23:48 UTC5d ago M0.8rising 6 – running 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 513 on average
527/ 550
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
426/ 450
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
57/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average
59/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
58/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 238 on average
161/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RustServer_5018?

Generated by the game, the map on RustServer_5018 is procedural, size 3,000 with seed 22314. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on RustServer_5018?

The name of RustServer_5018 gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on RustServer_5018?

At this moment, RustServer_5018 records 1 players across 50 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 6. The busiest point in the last 48 hours came at 10:00 UTC, averaging 3 players.

How does RustServer_5018 rank against other Rust servers?

Over the last seven days, RustServer_5018 recorded enough player hours to reach #3,953 worldwide, placing it in the top 18% of all ranked servers.

Server facts

How reliably does RustServer_5018 stay online?

As recorded now, RustServer_5018 is running. Going by the uptime figure it reports, it restarted about 5 days 11 hours ago. 119 of 120 hours in the last 5 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 23 October 2026.

Does RustServer_5018 hold a steady tick rate?

Its average server fps over the last 48 hours was 107, and it never dropped below 73. At its highest, it carried 50,943 entities: buildings, deployables and the world's other contents. Its highest memory use was 2,535 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does RustServer_5018 run from?

No region is published by RustServer_5018. 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 133.88.106.75:28015.

Which Rust version is RustServer_5018 running?

RustServer_5018 is running Rust network protocol 2635 and build 168909 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on RustServer_5018?

The recent wipes averaged a busiest count of 6 players. The peak on the most recent wipe came 31 hours after the wipe.

On what timetable does RustServer_5018 run its wipes?

The rhythm of RustServer_5018 cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 5 days 13 hours.

Lists and tags

What do the server tags on RustServer_5018 mean?

These are the tags RustServer_5018 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 RustServer_5018 appear?

You will find RustServer_5018 on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Connecting

What steps get you onto RustServer_5018?

You can connect by pressing F1 in Rust and typing client.connect 133.88.106.75:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.