Rust Data

rustdata.spaceservers133.88.122.166:28017.ipynb

Run all rust-data · live

‹ All servers

Online 133.88.122.166:28015 checked 12m ago

RustServer_2757

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak 1
rank #6,456 # top 29%
last wipe 8d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75103:0012:0021:0006:0015:0001:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510003:0012:0021:0006:0015:0001: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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

usual gap7.8 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held25%else halves by day 3

The first 48 hours of its last wipes

Tue 20 OctTue 13 OctThu 1 Oct
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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 07:52 UTC8d ago 1 NaN running 0
1 Tue 13 Oct, 00:09 UTC16d ago 1 halved by day 3 7.3 days 0
2 Thu 1 Oct, 23:39 UTC FW27d ago 1 halved by day 2 11 days 0
3 Wed 23 Sep, 15:34 UTC35d ago 1 held half 8.3 days 0
4 Thu 17 Sep, 02:33 UTC42d ago 1 halved by day 5 6.5 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.

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

Map

3000 · seed 55847
Map of RustServer_2757
map
Procedural Map
size
3000
seed
55847
Open on RustMaps

Server

srv.info()
address
133.88.122.166:28015
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 07:52 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
0ShockRust | Blue | NoLimitno group limit · 155 on average27/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average130/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average37/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average13/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average1/1000

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does RustServer_2757 rank?

Rank #6,456 on seven-day player hours for RustServer_2757, within the top 29% of all ranked servers.

How full does RustServer_2757 run?

The sample now reads 0 players for RustServer_2757, out of 20 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 0 players.

Server data

How well does RustServer_2757 perform?

Averaged over 48 hours: 70 server fps, never under 49. Buildings, deployables and all else in the world took the count as high as 49,090 entities. The memory field tops out at 2,243 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is RustServer_2757 on?

The build is Rust network protocol 2635 and build 168909 on Linux, run by RustServer_2757. Joining needs the same protocol on your game; Steam handles the update.

How reliable is RustServer_2757, and is it up?

Online is the state at the latest refresh for RustServer_2757. A restart about 4 days 3 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.

Which location does RustServer_2757 run from?

There is no region published for RustServer_2757. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 133.88.122.166:28015.

Rules, settings, map

Which settings and rules does RustServer_2757 run?

The name RustServer_2757 carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has RustServer_2757 selected?

Size 3,000, seed 55847: the procedural map on RustServer_2757, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

When does RustServer_2757 wipe, and on what schedule?

Irregular wipe times on RustServer_2757 leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 8 days 19 hours ago, and that is the one in play.

What is wipe day on RustServer_2757 like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in. Recent wipes kept the crowd above half the peak until the next wipe 25% of the time. In the wipes where it did not hold, half was lost by day 3.

Tags and filters

Where does RustServer_2757 appear among Rust Data lists and filters?

These Rust Data lists include RustServer_2757: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on RustServer_2757 hold?

Read by the game's server browser, the tags RustServer_2757 publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join RustServer_2757?

Enter client.connect 133.88.122.166: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 mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players 20 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 37,024 players 11,692 servers online