Rust Data

rustdata.spaceservers160.251.253.229:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.253.229:28015 checked 10m ago

RustServer_11987

Connect

srv = rust.server("160.251.253.229:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #15,191 # top 68%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75116:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020016:0001:0010:0020:0005:0014: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 14:25 UTC27d ago 2 NaN running 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.

display(srv.map, srv.info())

Map

3000 · seed 28916
Map of RustServer_11987
map
Procedural Map
size
3000
seed
28916
Open on RustMaps

Server

srv.info()
address
160.251.253.229:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 14:25 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average476/575
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average449/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 286 on average840/250
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average57/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 270 on average727/250
5Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average26/250

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does RustServer_11987 rank?

Rank #15,191 on seven-day player hours for RustServer_11987, within the top 68% of all ranked servers.

How full does RustServer_11987 run?

The sample now reads 0 players for RustServer_11987, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 14:00 UTC, mean 0 players.

Server data

How well does RustServer_11987 perform?

The 48-hour average is 134 server fps, with a low of 97. Buildings, deployables and all else in the world took the count as high as 44,225 entities. The memory field tops out at 1,810 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on RustServer_11987?

Rust network protocol 2635 and build 168909 on Linux is what RustServer_11987 runs. The protocol has to match before you can join, and Steam does the updating.

Is RustServer_11987 up, and what does its uptime show?

The current sample puts RustServer_11987 online. A restart about 2 days 1 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

Where does RustServer_11987 sit?

For RustServer_11987, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.251.253.229:28015.

Map and rules

Which settings and rules does RustServer_11987 run?

You will not find a gather rate in the string RustServer_11987. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.

What is the map on RustServer_11987?

The game generates the map on RustServer_11987: procedural, size 3,000, seed 28916. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does RustServer_11987 wipe?

The record for RustServer_11987 holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days ago.

On RustServer_11987, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 16 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold RustServer_11987, and which filters?

These Rust Data lists include RustServer_11987: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on RustServer_11987 hold?

The game's server browser reads these tags from RustServer_11987: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join RustServer_11987?

Enter client.connect 160.251.253.229:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players Slot count: 50.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$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.

Rust Data 91,534 players 11,873 servers online