Station XX-15454 · no signal
Wolves events validation
Offline 77.23.165.10:29115 checked 22m ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70%
- Last wipe
- 13h ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 slots
- Motion · 24 h
- M0.0■steady+0 players
- Events picked
- 1wipe on this record, in red
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 70% 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.6 daysbetween real wipes
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 21 Nov, 12:38 UTC23m ago | – | – | – | – | running | 0 |
| Fri 20 Nov, 23:10 UTC13h ago | – | – | – | – | – | 0 |
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 pageMap and rules
Which map is running on Wolves events validation?
Wolves events validation uses a procedural map, which the game generates.
Which settings and rules apply on Wolves events validation?
The name of Wolves events validation gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Wolves events validation right now?
Wolves events validation is not responding at this moment and is offline, last seen 22 minutes ago. Averaged across the last seven days, the population was 0 players.
How does Wolves events validation rank against other Rust servers?
Over the last seven days, Wolves events validation recorded enough player hours to reach #15,454 worldwide, placing it in the top 70% of all ranked servers.
Server facts
How reliably does Wolves events validation stay online?
Wolves events validation is down at the moment; the last recorded contact was 22 minutes ago. On 20 November 2026 it was recorded for the first time by Rust Server Trends.
Which region does Wolves events validation run from?
No region is published by Wolves events validation. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 77.23.165.10:29115 is the address it uses.
What build of Rust does Wolves events validation use?
Wolves events validation is running Rust network protocol 2636 and build 127089 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
How often does Wolves events validation wipe, and on which days?
The rhythm of Wolves events validation 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 3 December at 19:00 UTC. It has run its current world for 13 hours.
Lists and tags
What do the server tags on Wolves events validation mean?
These are the tags Wolves events validation publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp500 (Max players): The server has 500 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs127089-84fd9a97663 (Build): The build number is not made public; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Wolves events validation appear?
The Rust Server Trends lists that take in Wolves events validation are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Connecting
How do you connect to Wolves events validation?
You can connect by pressing F1 in Rust and typing client.connect 77.23.165.10:29115 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.