Rust Server Analytics 43,642 players11,650 servers
All servers
Drill-through Server detail

RustServer_17001

Online 133.88.119.159:28015 checked 10m ago

Drill-through
FilterServeris RustServer_17001
Attributes
Last refreshed
Players now 0/ 50
7-day average 0 peak 1
Rank #15,116 top 68%
Last wipe 27d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.250.50.75104:0013:0023:0008:0017:0002:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
02040608004:0013:0023:0008:0017:0002: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep2 Oct9 Oct16 Oct23 Oct30 Oct

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

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 gap2.4 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 09:30 UTC27d ago 1 – running 0
Thu 1 Oct, 09:25 UTC28d ago 1 – 1 days 0
Mon 28 Sep, 10:13 UTC31d ago 1 held half 3 days 0
Sat 26 Sep, 01:47 UTC34d ago 2 held half 2.4 days 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 482 on average 45 / 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 321 on average 80 / 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 284 on average 234 / 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 279 on average 7 / 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average 274 / 325
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 257 on average 268 / 275

Quick answers

from the figures on this page

Wipe data

When does RustServer_17001 wipe?

With irregular wipe times, RustServer_17001 offers no next wipe to predict. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. 27 days 18 hours ago the current world was made.

Wipe day on RustServer_17001: what should you expect?

Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 100% of cases.

Server

Which location hosts RustServer_17001?

A region is not published by RustServer_17001. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 133.88.119.159:28015.

What Rust build does RustServer_17001 run?

The platform is Linux, with Rust network protocol 2635 and build 168909 running on RustServer_17001. Your game must match the protocol to join, and Steam applies that update.

Is RustServer_17001 up, and how steady is its uptime?

The current status of RustServer_17001 is online. Its reported uptime indicates a restart roughly 3 days 7 hours ago. Of 168 hours in the last 7 full days, 145 were up: 86%. The first sighting of it by Rust Server Analytics was on 25 September 2026.

What performance does RustServer_17001 show?

The 48-hour average was 59 server fps; the low was 41. Entity count reached 93,460, covering buildings, deployables and the rest of the world. At its highest, memory use was 2,875 MB. Players experience lag as low fps combined with a rising entity count.

Lists and tags

Which meanings do the tags on RustServer_17001 carry?

Tags from RustServer_17001, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does RustServer_17001 appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count RustServer_17001 among their servers: Community Rust servers, live. It appears on the server list under the following filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player numbers

Against other Rust servers, how does RustServer_17001 compare?

Player hours for the last seven days place RustServer_17001 at #15,116, in the top 68% of the ranked field.

How many players does RustServer_17001 carry?

Of 50 slots, 0 are filled on RustServer_17001 at this refresh. The seven-day mean is 0 players, against a peak of 1. Across the last 48 hours, 21:00 UTC shows the highest average: 0 players.

Settings

What are the settings on RustServer_17001, and its rules?

Gather rate is not mentioned in the name of RustServer_17001. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. Community is its listing; it is a community server. VAC, Valve's anti-cheat, is enabled.

What is the map for RustServer_17001?

The game generates a procedural map of size 4,000 with seed 2026680033 for RustServer_17001. The map is reproducible from its size and seed and can be seen on RustMaps from here.

How to join

How do you connect to RustServer_17001?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 133.88.119.159:28015.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code A region code is not 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.