Station XX-15304 · no signal
Testing server
Offline 95.26.143.2:28015 checked 27d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,304
- top 64%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M –not enough readings
Players
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 bestTop 64% of all ranked servers. 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.
- usual gap
- 0.3 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 30 Sep, 23:18 UTC27d ago | M0.0■steady | 1 | – | running | 1 | |
| Wed 30 Sep, 17:11 UTC28d ago | M0.0■steady | 1 | – | 0.3 days | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which settings and rules apply on Testing server?
The name of Testing server gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Testing server right now?
No players are recorded on Testing server at this moment; it is offline, and the last sighting was 27 days 19 hours ago.
How does Testing server rank against other Rust servers?
On player hours for the past week, Testing server sits at #15,304, which puts it inside the top 64% of every ranked server.
Operator and location
How reliably does Testing server stay online?
Testing server is down at the moment; the last recorded contact was 27 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 30 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Testing server run from?
No region is published by Testing server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 95.26.143.2:28015 is the address it uses.
Which Rust version is Testing server running?
On Windows, Testing server runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Testing server?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does Testing server wipe, and on which days?
The rhythm of Testing server cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 27 days 19 hours.
Lists and tags
What do the server tags on Testing server mean?
Tags published by Testing server and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): 1 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Testing server appear?
The Rust Server Trends lists that take in Testing server are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to Testing server?
Enter client.connect 95.26.143.2:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.