Testing server
Offline 95.26.136.88:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
100% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 1/100
- 0/50
- 3/50
- 1/50
- 3/100
- 170/500
Quick answers
from the figures on this pageReset cycle
What wipe timing does Testing server follow?
The rhythm of Testing server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 43 days 20 hours ago.
Tags
How should you read the tags on Testing server?
These are the tags Testing server publishes, and the server browser reads them: gmhardcore (Game mode): Check: ruleset. Hardcore, the harsher option; mp1 (Max players): Slots: 1; ts0 (Group limit): Team play is disabled; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Testing server?
Rust Metrics lists featuring Testing server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o.
Population
Where does Testing server sit in the rankings?
Ranking for Testing server: #12,835 on seven-day player hours, top – of all ranked servers.
What player count does Testing server carry?
Reading for Testing server: offline at this moment; last seen 43 days 19 hours ago.
Operator and location
Which location does Testing server run from?
No region tag on Testing server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 95.26.136.88:28015.
What Rust version is Testing server on?
Rust network protocol 2633 and build 163794 on Windows is the build Testing server runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Testing server, and is it online?
Reading: offline. Testing server last answered 43 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 14 September 2026.
Settings and map
How is Testing server configured, and what rules are in force?
Reading the name gives no gather rate for Testing server. Check: group limit. None published. hardcore, Facepunch's most punishing mode — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on Testing server?
The game generates a procedural map for Testing server.
Join
How can you get onto Testing server?
Check: join. Open Rust, press F1, then enter client.connect 95.26.136.88:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.