testreality2
Online 45.11.95.88:11000 checked 10m ago
Server instruments
last reading Thu 10:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 236 · below 20 is lag, below 10 is badEntities
48 h range 2,339–4,460 · memory 1,429 MBUptime
3 days 12 hours since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 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 yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 13:10 UTC3d ago | 1 | – | running | 0 |
| Fri 9 Oct, 13:50 UTC19d ago | 0 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 7/100
- 2/100
- 1/100
- 9/200
- 3/400
- 5/400
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on testreality2?
At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 5 hours.
When does testreality2 wipe?
The rhythm of testreality2's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 3 days 23 hours ago.
Lists and filters
How should you read the tags on testreality2?
These are the tags testreality2 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts1 (Group limit): Team cap: 1; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; oxidation (Custom tag): Owner or plugin definition: this tag is not a standard Rust one. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show testreality2?
On Rust Metrics, testreality2 sits in these lists: Modded Rust servers, checked live and Solo-only 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.
Player count
What position does testreality2 hold among Rust servers?
Ranking for testreality2: #7,335 on seven-day player hours, top 33% of all ranked servers. Among servers in solo, it stands at #174.
What player count does testreality2 carry?
0 of 5 slots are filled on testreality2 right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.
Operator and location
What location is testreality2 hosted in?
No region comes from testreality2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 45.11.95.88:11000.
What Rust version is testreality2 on?
Reading: testreality2, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is performance on testreality2 within range?
Over the last 48 hours the average was 237 server fps; the floor was 236. Peak entity count: 4,460. Buildings, deployables and all else included. Reading: 1,534 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
Is testreality2 up, and how often does it stay up?
Check: connection. testreality2 is online at this moment. Check: restart. The uptime it reports puts the last restart about 3 days 12 hours ago. Uptime for the last 7 full days: 82 of 168 hours, or 49%. The first sighting on Rust Metrics was 25 September 2026.
Rules and settings
What rules does testreality2 enforce, and what are its settings?
Reading the name gives no gather rate for testreality2. Teams: none. The server is solo only. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.
What map is testreality2 on?
From seed 1337, the game generates the procedural map on testreality2. Its size is 1,000. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.
How to join
How can you get onto testreality2?
Press F1 in Rust and enter client.connect 45.11.95.88:11000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.