Station XX-15348 · recording
(Wunders) Dev & Testing
Online 195.201.167.33:28025 checked 10m ago
- Players now
- 0/ 25
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,348
- top 69%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 7d 21h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 25 slots
- Motion · 24 h
- M0.0■steady+0 players
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 35d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 22:37 UTC FW26d ago | M0.0■steady | 0 | – | running | 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 pageServer rules
Which map is running on (Wunders) Dev & Testing?
Generated by the game, the map on (Wunders) Dev & Testing is procedural, size 2,500 with seed 1234567. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on (Wunders) Dev & Testing?
No gather rate appears in the name of (Wunders) Dev & Testing. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on (Wunders) Dev & Testing?
At this moment, (Wunders) Dev & Testing records 0 players across 25 slots. Averaged across the last seven days, the population was 0 players.
How does (Wunders) Dev & Testing rank against other Rust servers?
Over the last seven days, (Wunders) Dev & Testing recorded enough player hours to reach #15,348 worldwide, placing it in the top 69% of all ranked servers.
Server details
How reliably does (Wunders) Dev & Testing stay online?
As recorded now, (Wunders) Dev & Testing is running. Its reported uptime points to a restart about 4 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does (Wunders) Dev & Testing hold a steady tick rate?
Across the last 48 hours it averaged 235 server fps, with a floor of 225. The world held up to 33,020 entities at its peak, buildings and deployables included. Its highest memory use was 1,559 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does (Wunders) Dev & Testing run from?
A region is not published by (Wunders) Dev & Testing. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 195.201.167.33:28025.
What build of Rust does (Wunders) Dev & Testing use?
Rust network protocol 2635 and build 168909 on Linux is what (Wunders) Dev & Testing runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on (Wunders) Dev & Testing?
On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does (Wunders) Dev & Testing run its wipes?
The force wipe is the only wipe (Wunders) Dev & Testing takes, once a month. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 26 days 22 hours.
Lists and tags
What do the server tags on (Wunders) Dev & Testing mean?
The game's server browser reads the tags (Wunders) Dev & Testing publishes: gmrust (Game mode): Survival in standard Rust; mp25 (Max players): 25 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 (Wunders) Dev & Testing appear?
These Rust Server Trends lists include (Wunders) Dev & Testing: Modded Rust servers, tracked live. These filters bring it up 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 (Wunders) Dev & Testing?
You can connect by pressing F1 in Rust and typing client.connect 195.201.167.33:28025 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.