Rust Server TrendsSeismic network · station log
Recording Stations11,709 Players54,841 Active3,244 Wipes · 3 h155 48 h

Station XX-15178 · recording

RustServer_17001

Online 133.88.119.159:28015 checked 6m ago

Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#15,178
top 68%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15178 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Wed 21:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

025507510011:0020:0005:0013:0023:0008: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 25 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
15k10k15k20k25 Sep2 Oct9 Oct15 Oct22 Oct29 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
2.4 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctThu 1 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 09:30 UTC27d ago M0.0rising 1 – running 0
Thu 1 Oct, 09:25 UTC28d ago M0.0rising 1 – 1 days 0
Mon 28 Sep, 10:13 UTC31d ago M0.0rising 1 held half 3 days 0
Sat 26 Sep, 01:47 UTC33d ago M0.3rising 2 held half 2.4 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 519 on average
393/ 400
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
339/ 350
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
38/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average
34/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
47/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 244 on average
157/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on RustServer_17001?

Generated by the game, the map on RustServer_17001 is procedural, size 4,000 with seed 2026680033. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on RustServer_17001?

The name of RustServer_17001 gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on RustServer_17001 right now?

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

How does RustServer_17001 rank against other Rust servers?

Over the last seven days, RustServer_17001 recorded enough player hours to reach #15,178 worldwide, placing it in the top 68% of all ranked servers.

Server facts

How reliably does RustServer_17001 stay online?

Right now, you can reach RustServer_17001. The uptime it reports puts its last restart about 2 days 13 hours ago. 145 of 168 hours in the last 7 full days were up time, 86% of the total. 25 September 2026 is when Rust Server Trends first recorded it.

How well does RustServer_17001 perform under load?

The 48-hour average is 69 server fps; 41 is the lowest observed. At its highest, it carried 93,460 entities: buildings, deployables and the world's other contents. Its highest memory use was 2,842 MB. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is RustServer_17001 hosted?

Nothing about a region comes from RustServer_17001. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 133.88.119.159:28015 is the address it uses.

What build of Rust does RustServer_17001 use?

RustServer_17001 is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on RustServer_17001?

On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

On what timetable does RustServer_17001 run its wipes?

No next wipe can be predicted for RustServer_17001, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days.

Server tags

What do the server tags on RustServer_17001 mean?

These are the tags RustServer_17001 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. 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_17001 appear?

These Rust Server Trends lists include RustServer_17001: 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.

Connecting

What steps get you onto RustServer_17001?

To join, enter client.connect 133.88.119.159:28015 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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players Slots: 50.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.