Testing server
Offline 95.26.147.207:28015 checked 40d 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- 5/100
- 1/50
- 1/50
- 6/50
- 0/100
- 52/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 40 days 1 hours ago.
Tag meanings
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): Hardcore ruleset, the harsher one; mp1 (Max players): Slots: 1; ts0 (Group limit): Team play is disabled; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Testing server appear in Rust Metrics lists and filters?
On Rust Metrics, Testing server sits in these lists: 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
What position does Testing server hold among Rust servers?
Player hours over seven days put Testing server at #13,262, in the top – of all ranked servers.
How full does Testing server get?
Testing server is not responding; status offline, last seen 40 days ago.
Operator and location
Which location does Testing server run from?
No region comes from Testing server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 95.26.147.207:28015.
What Rust version is Testing server on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by Testing server. Check: protocol. To join, your game must match; Steam handles the update.
Is Testing server up, and how often does it stay up?
Testing server reports offline. The last reading came 40 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 17 September 2026.
Map and rules
How is Testing server configured, and what rules are in force?
No gather rate appears in the name: Testing server. Check: group limit. None published. The mode is hardcore. Note the following: Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Testing server?
Procedural map on Testing server, made by the game's generator.
How to join
How do you connect to Testing server?
Check: join. Open Rust, press F1, then enter client.connect 95.26.147.207:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.