Rust Data

rustdata.spaceservers165.140.179.51:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 165.140.179.51:28015 checked 1d ago

KAD test - Rust (Pterodactyl)

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0021:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040020:0021:0022: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 3 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
15k10k15k20k3 Oct8 Oct13 Oct17 Oct22 Oct27 Oct

Top 70% 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

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 Sat 3 Oct, 15:31 UTC24d 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

3500 · seed 4242
Map of KAD test - Rust (Pterodactyl)
map
Procedural Map
size
3500
seed
4242
Open on RustMaps

Server

srv.info()
address
165.140.179.51:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 15:31 UTC
hostname
–
first seen
3 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 · 501 on average784/825
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 347 on average50/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 342 on average125/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average463/500
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 281 on average268/300
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 258 on average196/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does KAD test - Rust (Pterodactyl) rank?

Over the last seven days KAD test - Rust (Pterodactyl) sits at #15,383 on player hours, in the top 70% of ranked servers.

How many players does KAD test - Rust (Pterodactyl) hold at once?

KAD test - Rust (Pterodactyl) returns no live count at this refresh, having last been seen 45 hours ago. Over the last seven days it averaged 0 players.

About the server

How smoothly does KAD test - Rust (Pterodactyl) run?

Server fps over the last 48 hours averages 157; the floor is 63. Entity numbers reached 71,144, and that includes buildings, deployables and the rest. The memory field tops out at 2,408 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does KAD test - Rust (Pterodactyl) run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by KAD test - Rust (Pterodactyl). The protocol has to match before you can join, and Steam does the updating.

How reliable is KAD test - Rust (Pterodactyl), and is it online now?

The latest sample has KAD test - Rust (Pterodactyl) offline, with a last sighting 45 hours ago. The uptime it reports puts the last restart about 2 days 20 hours ago. 143 of 168 hours up over the last 7 full days, or 85%. The first row Rust Data holds for it is dated 3 October 2026.

Where does KAD test - Rust (Pterodactyl) sit?

For KAD test - Rust (Pterodactyl), no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 165.140.179.51:28015.

Settings and map

Which rules apply on KAD test - Rust (Pterodactyl), and what settings?

You will not find a gather rate in the string KAD test - Rust (Pterodactyl). The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

What is the map on KAD test - Rust (Pterodactyl)?

Size 3,500, seed 4242: the procedural map on KAD test - Rust (Pterodactyl), generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does KAD test - Rust (Pterodactyl) wipe, and how often?

A rhythm cannot be read from the wipes of KAD test - Rust (Pterodactyl) on record, which are too few. 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 24 days 4 hours ago.

What is wipe day on KAD test - Rust (Pterodactyl) like?

Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does KAD test - Rust (Pterodactyl) appear among Rust Data lists and filters?

The Rust Data lists that KAD test - Rust (Pterodactyl) fits are: 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.

How should you read the server tags on KAD test - Rust (Pterodactyl)?

The game's server browser reads these tags from KAD test - Rust (Pterodactyl): gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is 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.

Connecting

What is the way to join KAD test - Rust (Pterodactyl)?

Enter client.connect 165.140.179.51: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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 92,145 players 11,896 servers online