Skip to the page
Network live 11,814 servers online 69,594 players aboard 187 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

testreality2

Online 45.11.95.88:11000 checked 11m ago

solo moddedoxide
Tracking number · connect
Wipe progress · wiped 4d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
0/ 5 players now 0% full
07-day averagepeak 1
#7,341ranktop 33%
4d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

AveragePeak
00.250.50.75114:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Server performance

010020030040014:0023:0008:0016:0002:0011: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
RankRank in region
15k10k15k20k25 Sep29 Sep9 Oct13 Oct25 Oct29 Oct

Top 33% of all ranked servers, and #174 of the solo servers (top 78%). Ranked on player hours over the last seven days.

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.

16 daysusual gapbetween real wipes
0wipe-day peakplayers, 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

every wipe as a delivery, newest first
  1. Sun 25 Oct, 13:10 UTC 13:10 UK · 4d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Fri 9 Oct, 13:50 UTC 14:50 UK · 19d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    16 days
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. SOLO ONLY | FULL WIPE 22.10 | UA | EU | ПАЛЯНИЦЯ | UKREU · solo · weekly · 15 on average 4 / 100
  2. 【疾风】5倍|单人|独狼|10.23新档|新手|快速入门EA · solo · weekly · 14 on average 2 / 100
  3. [LATAM] Estrella Solitaria SOLO ONLY | 26/10 WipeSA · solo · weekly · 9 on average 0 / 100
  4. [GUA] MODDED 2Х | SOLO | EU | MAP WIPE 27.10EU · solo · weekly · 5 on average 7 / 200
  5. 404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10EU · solo · monthly · 5 on average 3 / 400
  6. 404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10EU · solo · monthly · 3 on average 3 / 400
Help desk

Quick answers

From the figures on this page.

Player activity

Where does testreality2 place among Rust servers?

In the top 33% of all ranked servers sits testreality2, at #7,341 on hours played over seven days. The solo group puts it at #174.

What is the current population on testreality2?

The current count is 0 players on 5 slots for testreality2. The seven-day figures show an average of 0 players and a peak of 1. Over the last 48 hours, the peak hour came at 09:00 UTC with an average of 1 players.

Rules and settings

What is the current map on testreality2?

The game generates the procedural map on testreality2 at size 1,000 with seed 1337. Identical size and seed give an identical map: view it on RustMaps from this page. Its name for the map: Custom Map.

What settings and rules should you know for testreality2?

You will not find a gather rate in the name of testreality2. Solo play only: teams are not allowed. survival is the mode, the usual game: build, gather, raid. You can raid and fight other players. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. The VAC anti-cheat from Valve is disabled.

Operator and location

What location does testreality2 run from?

You will find no region published by testreality2. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 45.11.95.88:11000.

Does testreality2 perform well?

Averaged over the last 48 hours, server fps was 237, with a low of 236. Buildings, deployables and all the rest of the world pushed its entity count as high as 4,460. The highest memory reading was 1,534 MB. Lag, to players, means low fps alongside an entity count on the rise.

What is the uptime of testreality2, and is it online?

You can find testreality2 online at present. The uptime it reports puts its last restart at about 3 days 13 hours ago. 49% is the uptime for the last 7 full days, up for 82 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 25 September 2026.

On what Rust version does testreality2 operate?

The version on testreality2 is Rust network protocol 2635 and build 168909, running on Windows. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe times

What should you expect from wipe day on testreality2?

The average busiest point of its recent wipes was 0 players. On the latest wipe, 5 hours passed before the crowd peaked.

How often does testreality2 wipe, and at what times?

There are too few of testreality2's wipes on record so far to show its rhythm. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. The world it is running was made 4 days.

Tags and filters

Where does testreality2 appear in Rust Wipe Tracker lists and filters?

The Rust Wipe Tracker lists that include testreality2 are: Modded Rust servers and Solo Rust servers. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Last wipe: In the last week.

What is the meaning of the server tags on testreality2?

The game's server browser picks up these testreality2 tags: gmrust (Game mode): Standard Rust survival is the game mode here; mp5 (Max players): Slot count: 5; ts1 (Group limit): Teams are limited to 1 players; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; oxidation (Custom tag): Set by the owner or a plugin, it isn't a standard Rust tag. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

How do you connect to testreality2?

Enter client.connect 45.11.95.88:11000 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game mode here.
mp5
Max players Slot count: 5.
ts1
Group limit Teams are limited to 1 players.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

oxidation
Custom tag Set by the owner or a plugin, it isn't a standard Rust tag.

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.