Rust Server TrendsSeismic network · station log
Recording Stations11,614 Players34,171 Active2,816 Wipes · 3 h69 48 h

Station XX-7572 · recording

testreality2

Online 45.11.95.88:11000 checked 10m ago

solo moddedoxide
Connect
Players now
0/ 5
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#7,572
top 34%
Last wipe
3d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-7572 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 5 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Tue 12:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040007:0016:0001:0010:0020:0005: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.

Channel 3 · rank movement

Rank

daily · 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.

Expected events

Wipe schedule

too few wipes seen yet

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

usual gap
16 daysbetween real wipes
wipe-day peak
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 25 Oct, 13:10 UTC3d ago M0.0rising 1 – running 0
Fri 9 Oct, 13:50 UTC19d ago M0.0steady 0 – 16 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
0/ 100
16/ 100
[LATAM] Estrella Solitaria SOLO ONLY | 26/10 Wipe SA · solo · weekly · 11 on average
6/ 100
[GUA] MODDED 2Х | SOLO | EU | MAP WIPE 27.10 EU · solo · weekly · 5 on average
2/ 200
404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10 EU · solo · monthly · 5 on average
2/ 400
404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10 EU · solo · monthly · 3 on average
6/ 400
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on testreality2?

Generated by the game, the map on testreality2 is procedural, size 1,000 with seed 1337. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on testreality2?

You will find no gather rate in the name of testreality2. No teams: solo play only. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC off, Valve's anti-cheat.

Player counts

What is the current population on testreality2?

At this moment, testreality2 records 0 players across 5 slots. Across seven days this server recorded an average of 0 players and a peak of 1. The busiest point in the last 48 hours came at 12:00 UTC, averaging 1 players.

How does testreality2 rank against other Rust servers?

On player hours for the past week, testreality2 sits at #7,572, which puts it inside the top 34% of every ranked server. Within solo, it places #173.

Operator and location

How reliably does testreality2 stay online?

Right now, you can reach testreality2. Its reported uptime points to a restart about 3 days 7 hours ago. It was up 49% of the time across the last 7 full days: 82 of 168 hours. 25 September 2026 is when Rust Server Trends first recorded it.

Does testreality2 hold a steady tick rate?

Its average server fps over the last 48 hours was 237, and it never dropped below 236. The world held up to 4,460 entities at its peak, buildings and deployables included. Its highest memory use was 1,534 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does testreality2 run from?

No region is published by testreality2. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 45.11.95.88:11000.

What build of Rust does testreality2 use?

testreality2 is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on testreality2?

On average, the busiest point of its recent wipes drew 0 players. 5 hours into the latest wipe, the crowd reached its peak.

How often does testreality2 wipe, and on which days?

Too few wipes of testreality2 are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 3 days 17 hours is how long the current world has been running.

Server tags

What do the server tags on testreality2 mean?

These are the tags testreality2 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): The server has 5 slots; ts1 (Group limit): Teams are capped at 1 players; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; oxidation (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does testreality2 appear?

These Rust Server Trends lists include testreality2: Modded Rust servers, tracked live and Solo Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Last wipe: In the last week.

Join the server

What steps get you onto testreality2?

To join, enter client.connect 45.11.95.88:11000 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp5,ptrak,$r?,v2635,gmrust,cs168909,ts1,^o^z,oxidation

Game

gmrust
Game mode You'll find standard Rust survival here.
mp5
Max players The server has 5 slots.
ts1
Group limit Teams are capped at 1 players.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Other

oxidation
Custom tag The owner or a plugin set this tag, and it's not one of Rust's standard tags.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.