Rust Data

rustdata.spaceservers193.135.10.247:15051.ipynb

Run all rust-data · live

‹ All servers

Online EU 193.135.10.247:15050 checked 12m ago

TypicalRustGameplay

Connect

srv = rust.server("193.135.10.247:15051")
print(srv.connect_command)

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak –
rank #15,268 # top 68% · #2528 in EU
last wipe 13d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608022:0007:0016:0002:0011:0020: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 16 Oct. 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
15k10k15k20k16 Oct19 Oct21 Oct24 Oct26 Oct29 Oct

Top 68% of all ranked servers, top 87% in EU. 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 peak3players, 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 3, 24 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 20:38 UTC13d ago 3 NaN running 2

# 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

3500 · seed 17475
Map of TypicalRustGameplay
map
Procedural Map
size
3500
seed
17475
Open on RustMaps

Server

srv.info()
address
193.135.10.247:15050
region
EU
max players
20
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 20:38 UTC
hostname
–
first seen
16 Oct 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 · 506 on average198/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average276/300
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 282 on average737/800
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average42/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average818/900
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 242 on average651/725

Quick answers

From the figures on this page.

Population

How does TypicalRustGameplay compare in the rankings?

On seven-day player hours TypicalRustGameplay is #15,268 overall and #2,528 in Europe, inside the top 68% of all ranked servers.

What population does TypicalRustGameplay carry?

TypicalRustGameplay reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players.

About the server

How well does TypicalRustGameplay perform?

The 48-hour average is 49 server fps, with a low of 41. Entity numbers reached 65,425, and that includes buildings, deployables and the rest. The memory field tops out at 3,471 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is TypicalRustGameplay on?

The build is Rust network protocol 2634 and build 167781 on Linux, run by TypicalRustGameplay. Steam updates your game for you, but the protocol must match to join.

Is TypicalRustGameplay up, and what does its uptime show?

Online is the state at the latest refresh for TypicalRustGameplay. A restart about 11 days 4 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 16 October 2026.

Which location does TypicalRustGameplay run from?

The EU tag is what TypicalRustGameplay uses to list itself in Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. 193.135.10.247:15050 is its address.

Rules, settings, map

Which rules apply on TypicalRustGameplay, and what settings?

You will not find a gather rate in the string TypicalRustGameplay. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Community is its browser category. Anti-cheat status: VAC on.

Which map has TypicalRustGameplay selected?

The game generates the map on TypicalRustGameplay: procedural, size 3,500, seed 17475. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

When does TypicalRustGameplay wipe, and on what schedule?

A rhythm cannot be read from the wipes of TypicalRustGameplay on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 13 days 1 hours ago, and that is the one in play.

What is wipe day on TypicalRustGameplay like?

Recent wipes averaged 3 players at their peak. Peak population on the latest wipe came 24 hours in.

Lists and tags

Which Rust Data filters and lists contain TypicalRustGameplay?

On Rust Data, TypicalRustGameplay appears in these lists: EU Rust servers and Rust community servers, unfiltered. Under these filters on the server list, it is listed: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on TypicalRustGameplay?

These tags are published by TypicalRustGameplay and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): Slot count: 20; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; EU (Europe): The server browser files it under Europe. 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 to join TypicalRustGameplay?

Enter client.connect 193.135.10.247:15050 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?,v2634,EU,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp20
Max players Slot count: 20.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Region

EU
Europe The server browser files it under Europe.

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 86,322 players 11,829 servers online