Rust Data LabData lab · live
Live readings Servers11,680 Players52,558 Populated3,201 Fresh wipes · 3h137 Sampled every 5 min

Element card · group Community · atomic number 15,179, its rank

RustServer_17001

Online 133.88.119.159:28015 checked 10m ago

Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak 1
Rank · atomic number#15,179top 68%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.250.50.75110:0019:0004:0013:0023:0008:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
025507510010:0019:0004: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.

Result 03

Rank

Result

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.

Reaction kinetics

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.

Reaction log

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 UTC30d ago 1 held half 3 days 0
Sat 26 Sep, 01:47 UTC33d 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
  1. 1 Ru Rusty Moose |E… 355
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 522 on average 355/ 375
  2. 2 Ru Rustoria.co - … 327
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 327/ 325
  3. 3 Ru Rusty Moose |E… 33
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 33/ 250
  4. 4 Ru Rustoria.co - … 34
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 34/ 250
  5. 5 Ru Rustafied.com … 55
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 55/ 100
  6. 6 Ru Rustoria.co - … 168
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 246 on average 168/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on RustServer_17001?

A procedural map of size 4,000 with seed 2026680033 runs on RustServer_17001, generated by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map.

What settings and rules apply on RustServer_17001?

Nothing in the name of RustServer_17001 gives a gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. You will find it under Community in the server browser. VAC is on, Valve's anti-cheat.

Server facts

Which location is RustServer_17001 based in?

There is no region on record for RustServer_17001. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 133.88.119.159:28015.

Which Rust version is RustServer_17001 on?

On Linux, RustServer_17001 is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

Does RustServer_17001 stay up, and how reliable is its uptime?

Right now, RustServer_17001 is reachable. About 2 days 13 hours ago is when it last restarted, based on its uptime. For the last 7 full days, 145 of 168 hours were online, giving 86% uptime. It first appeared to Rust Data Lab on 25 September 2026.

Is RustServer_17001 known for smooth running?

The last 48 hours show an average of 69 server fps and a minimum of 41. The entity count reached 93,460, including buildings, deployables and all other world items. The highest memory usage was 2,842 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe days

What is the wiping pattern on RustServer_17001?

With no fixed rhythm, RustServer_17001 wipes at irregular times, so the next wipe cannot be predicted. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 27 days ago.

What does a typical wipe day on RustServer_17001 involve?

Averaged across its recent wipes, the busiest point drew 1 players. 1 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 100% of its recent wipes.

Tags, lists

What should you understand from the tags RustServer_17001 carries?

gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Player slots: 50; ts8 (Group limit): 8 per team, the default the game ships with; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set: that is the tag list RustServer_17001 publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does RustServer_17001 appear in?

These themed Rust Data Lab lists carry RustServer_17001: Rust community servers, measured. Applying these filters on the server list returns it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player numbers

What position does RustServer_17001 hold among Rust servers?

Player hours over the last week put RustServer_17001 at #15,179, inside the top 68% of ranked servers.

What does the current player count on RustServer_17001 tell you?

Of 50 slots, 0 are taken on RustServer_17001 right now. A seven-day sample gives 0 players on average and 1 at the top. The busiest point in the last 48 hours came at 21:00 UTC, averaging 0 players.

How to join

What is the way to join RustServer_17001?

Open the console with F1 in Rust and type client.connect 133.88.119.159:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players Player slots: 50.
ts8
Group limit 8 per team, the default the game ships with.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is 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.