Rust Data

rustdata.spaceservers136.243.173.254:7163.ipynb

Run all rust-data · live

‹ All servers

Online 136.243.173.254:7161 checked 13m ago

EU | WIPEZERO| NO TEAM LIMIT

Connect

srv = rust.server("136.243.173.254:7163")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,353 # top 69%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet

Players

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

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040003: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 21 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
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

Top 69% 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 peak1players, last three wipes

The first 48 hours of its last wipes

01234+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 Fri 2 Oct, 13:27 UTC26d ago 1 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

4000 · seed 436605065
Map of EU | WIPEZERO| NO TEAM LIMIT
map
Procedural Map
size
4000
seed
436605065
Open on RustMaps

Server

srv.info()
address
136.243.173.254:7161
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 13:27 UTC
hostname
–
first seen
21 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 · 560 on average169/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average121/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average17/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 288 on average15/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average18/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average29/200

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does EU | WIPEZERO| NO TEAM LIMIT rank?

Over the last seven days EU | WIPEZERO| NO TEAM LIMIT sits at #15,353 on player hours, in the top 69% of ranked servers.

How many players does EU | WIPEZERO| NO TEAM LIMIT hold at once?

Current row: 0 players on EU | WIPEZERO| NO TEAM LIMIT, against 100 slots. Over the last seven days it averaged 0 players.

Server data

What does performance look like on EU | WIPEZERO| NO TEAM LIMIT?

Averaged over 48 hours: 177 server fps, never under 118. The entity count peaked at 94,176, covering buildings, deployables and the rest of the world. The memory field tops out at 2,600 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does EU | WIPEZERO| NO TEAM LIMIT run?

Rust network protocol 2635 and build 168909 on Linux is what EU | WIPEZERO| NO TEAM LIMIT runs. Joining needs the same protocol on your game; Steam handles the update.

Is EU | WIPEZERO| NO TEAM LIMIT up, and what does its uptime show?

The current sample puts EU | WIPEZERO| NO TEAM LIMIT 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 21 September 2026.

Which location does EU | WIPEZERO| NO TEAM LIMIT run from?

No region tag is published by EU | WIPEZERO| NO TEAM LIMIT, though its name points to Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 136.243.173.254:7161.

Settings and map

What rules and settings are recorded for EU | WIPEZERO| NO TEAM LIMIT?

No gather rate appears in the name: EU | WIPEZERO| NO TEAM LIMIT. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has EU | WIPEZERO| NO TEAM LIMIT loaded?

EU | WIPEZERO| NO TEAM LIMIT runs a procedural map of size 4,000 with seed 436605065, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

When does EU | WIPEZERO| NO TEAM LIMIT wipe, and how often?

Too few wipes are on record for EU | WIPEZERO| NO TEAM LIMIT to reveal its rhythm. 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 26 days 13 hours ago, and that is the one in play.

What is wipe day on EU | WIPEZERO| NO TEAM LIMIT like?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began.

Tags and filters

Which lists on Rust Data hold EU | WIPEZERO| NO TEAM LIMIT, and which filters?

On Rust Data, EU | WIPEZERO| NO TEAM LIMIT appears in these lists: EU Rust servers and Rust community servers, unfiltered. It appears under these filters on the server list: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on EU | WIPEZERO| NO TEAM LIMIT hold?

The game's server browser reads these tags from EU | WIPEZERO| NO TEAM LIMIT: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into EU | WIPEZERO| NO TEAM LIMIT?

In Rust, F1 opens the console: type client.connect 136.243.173.254:7161. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: 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.

Rust Data 38,590 players 11,700 servers online