Rust Data

rustdata.spaceservers45.11.95.88:11001.ipynb

Run all rust-data · live

‹ All servers

Online 45.11.95.88:11000 checked 7m ago

testreality2

solo moddedoxide

Connect

srv = rust.server("45.11.95.88:11001")
print(srv.connect_command)

Right now

srv.summary()
players now 0/5 # 0% full
7-day average 0 # peak 1
rank #7,575 # top 34%
last wipe 3d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75108:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040008:0017:0002:0011:0021:0006: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 25 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
15k10k15k20k25 Sep29 Sep9 Oct13 Oct25 Oct29 Oct

Top 34% of all ranked servers, and #173 of the solo servers (top 78%). 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.

usual gap16 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sun 25 OctFri 9 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 25 Oct, 13:10 UTC3d ago 1 NaN running 0
1 Fri 9 Oct, 13:50 UTC19d ago 0 NaN 16 days 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

1000 · seed 1337
Map of testreality2
map
Custom Map
size
1000
seed
1337

Server

srv.info()
address
45.11.95.88:11000
region
–
max players
5
group limit
solo
wipe schedule
–
last wipe
25 Oct 2026, 13:10 UTC
hostname
–
first seen
25 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0SOLO ONLY | FULL WIPE 22.10 | UA | EU | ПАЛЯНИЦЯ | UKREU · solo · weekly · 15 on average2/100
1【疾风】5倍|单人|独狼|10.23新档|新手|快速入门EA · solo · weekly · 14 on average16/100
2[LATAM] Estrella Solitaria SOLO ONLY | 26/10 WipeSA · solo · weekly · 11 on average5/100
3[GUA] MODDED 2Х | SOLO | EU | MAP WIPE 27.10EU · solo · weekly · 5 on average2/200
4404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10EU · solo · monthly · 5 on average2/400
5404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10EU · solo · monthly · 3 on average6/400

Quick answers

From the figures on this page.

Population data

What position does testreality2 take in the server rankings?

Over the last seven days testreality2 sits at #7,575 on player hours, in the top 34% of ranked servers. Within the solo group, its rank is #173.

How full does testreality2 run?

The sample now reads 0 players for testreality2, out of 5 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 1 players.

Server data

How smoothly does testreality2 run?

Server fps over the last 48 hours averages 237; the floor is 236. Buildings, deployables and all else in the world took the count as high as 4,460 entities. A high of 1,534 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on testreality2?

Rust network protocol 2635 and build 168909 on Windows is what testreality2 runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is testreality2, and is it online now?

Online is the state at the latest refresh for testreality2. A restart about 3 days 8 hours ago is what its reported uptime implies. Uptime of 49% across the last 7 full days: 82 hours of 168. Its earliest recorded date in Rust Data is 25 September 2026.

Which location does testreality2 run from?

For testreality2, no region is published. 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 45.11.95.88:11000.

Settings and map

Which rules apply on testreality2, and what settings?

The name testreality2 carries no gather rate. This server is solo only, with no teams. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.

Which map has testreality2 selected?

The game generates the map on testreality2: procedural, size 1,000, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.

Wipe schedule

When does testreality2 wipe, and on what schedule?

Too few wipes are on record for testreality2 to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 3 days 18 hours ago.

On testreality2, what happens on wipe day?

Recent wipes averaged 0 players at their peak. 5 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain testreality2?

The Rust Data lists that testreality2 fits are: Modded Rust servers and Solo Rust servers, group limit 1. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Last wipe: In the last week.

How should you read the server tags on testreality2?

Read by the game's server browser, the tags testreality2 publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts1 (Group limit): The team cap is 1; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; oxidation (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join testreality2?

In Rust, F1 opens the console: type client.connect 45.11.95.88:11000. 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 mp5,ptrak,$r?,v2635,gmrust,cs168909,ts1,^o^z,oxidation

Game

gmrust
Game mode Rust survival in its standard form.
mp5
Max players The server lists 5 slots.
ts1
Group limit The team cap is 1.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

Other

oxidation
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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 39,438 players 11,623 servers online