Rust Data

rustdata.spaceservers66.51.97.64:28016.ipynb

Run all rust-data · live

‹ All servers

Online EU 66.51.97.64:28015 checked 10m ago

Test

biweekly wipes moddedoxidepve

Connect

srv = rust.server("66.51.97.64:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69% · #2568 in EU
last wipe 27d ago # biweekly schedule
next wipe 14h # Thu 29 Oct, 18:08 UTC
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123405:0014:0023:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
0246805:0014:0023:0007:0016:0002: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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers, top 88% in EU. Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 29 October, 18:08 UTC, in 14h. # Its biweekly schedule tag · low confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
014hThu 29 Oct, 18:08 UTCwipe
17d 14hThu 5 Nov, 19:00 UTCFW force wipe
214d 14hThu 12 Nov, 18:08 UTCwipe
328d 14hThu 26 Nov, 18:08 UTCwipe
435d 14hThu 3 Dec, 19:00 UTCFW force wipe
542d 14hThu 10 Dec, 18:08 UTCwipe

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, 37 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:08 UTC FW27d 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 942019
Map of Test
map
Procedural Map
size
3500
seed
942019
Open on RustMaps

Server

srv.info()
address
66.51.97.64:28015
region
EU
max players
50
group limit
8, the default
wipe schedule
biweekly
last wipe
1 Oct 2026, 18:08 UTC
hostname
–
first seen
17 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 241 on average93/2000
1TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 51 on average12/100
2RustAria#4 [Мирный / PVE / SKINDROPS]EU · groups of 100+ · biweekly · 29 on average6/200
3[ESP] TIESOLAND PVE | SKILLS | EVENTOS | HOMEEU · groups of 8+ · biweekly · 27 on average2/50
4[EU/US] RustyWasteland PVE | Halloween Contest | Zombies | RaidEU · groups of 10+ · biweekly · 27 on average6/100
5PvE Rust-Z {х1-х5} Quest/Eco/Zombie/EventsEU · groups of 8+ · biweekly · 25 on average9/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Test rank?

Player hours over the last seven days: #15,349 for Test, #2,568 in Europe, within the top 69% of the ranked set.

What population does Test carry?

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

Server data

How smoothly does Test run?

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

What Rust version does Test run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Test. The protocol has to match before you can join, and Steam does the updating.

Is Test up, and what does its uptime show?

Test reports itself online at the current refresh. A restart about 5 days 7 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 17 September 2026.

Where does Test sit?

With its EU tag, Test lists itself in Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 66.51.97.64:28015 is its address.

Settings and map

Which settings and rules does Test run?

You will not find a gather rate in the string Test. No custom cap; the default of 8 players per group stands. pve is the game mode here, and player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Test loaded?

The game generates the map on Test: procedural, size 3,500, seed 942019. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

On what schedule does Test wipe?

The prediction follows the tag, because Test's wipes on record are too few to confirm the schedule. On Thursday 29 October at 18:08 UTC the next wipe is due. The world it runs now was generated 27 days 9 hours ago. A fortnightly wipe schedule is published in its tags.

On Test, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 37 hours after it began.

Tags, lists

Which Rust Data filters and lists contain Test?

These Rust Data lists include Test: EU Rust servers, Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

How should you read the server tags on Test?

These tags are published by Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): Europe is its listing in the server browser. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Test?

Enter client.connect 66.51.97.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 mp50,ptrak,$r?,v2635,^p,^b,EU,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EU
Europe Europe is its listing in the server browser.

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 33,003 players 11,659 servers online