Rust Data

rustdata.spaceservers93.137.36.64:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 93.137.36.64:28015 checked 34d ago

Testing1

Connect

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

Right now

srv.summary()
players now 1/2 # 50% full
7-day average 0 # peak –
rank #13,515 # top 60%
last wipe 34d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. 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
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
93.137.36.64:28015
region
–
max players
2
group limit
8, the default
wipe schedule
–
last wipe
24 Sep 2026, 16:45 UTC
hostname
–
first seen
24 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 average448/500
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average454/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 286 on average984/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average67/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 270 on average998/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average22/250

Quick answers

From the figures on this page.

Population data

What position does Testing1 take in the server rankings?

Rank #13,515 on seven-day player hours for Testing1, within the top 60% of all ranked servers.

What population does Testing1 carry?

The current row shows Testing1 offline; the last response was 34 days 20 hours ago.

Server data

What is the Rust version on Testing1?

The build is Rust network protocol 2633 and build 165217 on Windows, run by Testing1. Joining needs the same protocol on your game; Steam handles the update.

Is Testing1 up, and what does its uptime show?

The latest sample has Testing1 offline, with a last sighting 34 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 24 September 2026.

Which location does Testing1 run from?

For Testing1, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 93.137.36.64:28015 is its address.

Rules, settings, map

Which rules apply on Testing1, and what settings?

No gather rate appears in the name: Testing1. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. 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 Testing1?

The game generates its map: procedural, on Testing1.

Wipe data

When does Testing1 wipe, and on what schedule?

The record for Testing1 holds too few wipes to show a 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 34 days 23 hours ago, and that is the one in play.

Tags, lists

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

The Rust Data lists that Testing1 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Testing1 hold?

These tags are published by Testing1 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. 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.

Join steps

How can I connect to Testing1?

Enter client.connect 93.137.36.64: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 mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp2
Max players The server lists 2 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs165217
Build The server runs build 165217.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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 94,751 players 11,875 servers online