Station XX-15876 · no signal
Wizla's Test Server
Offline 84.67.167.117:28015 checked 20d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,876
- top 72%
- Last wipe
- 20d 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 72% 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
- 18 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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 |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 23:14 UTC20d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 20 Sep, 22:56 UTC38d ago | M0.0▲rising | 1 | held half | 18 days | 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 settings and rules apply on Wizla's Test Server?
The name of Wizla's Test Server gives no gather rate. At the game's default, groups can have up to 8 players. build & creative is the game mode, building in a sandbox, and no gathering. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched off.
Population
What is the current population on Wizla's Test Server?
A reading taken now finds Wizla's Test Server offline; the most recent activity was 20 days ago.
How does Wizla's Test Server rank against other Rust servers?
On player hours for the past week, Wizla's Test Server sits at #15,876, which puts it inside the top 72% of every ranked server.
Operator and location
How reliably does Wizla's Test Server stay online?
No contact with Wizla's Test Server right now, and the last recorded contact was 20 days ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 20 September 2026.
Where in the world is Wizla's Test Server hosted?
A region is not published by Wizla's Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 84.67.167.117:28015.
What build of Rust does Wizla's Test Server use?
Wizla's Test Server is running Rust network protocol 2634 and build 167231 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Wizla's Test Server?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
How often does Wizla's Test Server wipe, and on which days?
On record so far are too few of Wizla's Test Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 20 days 2 hours is how long the current world has been running.
Server tags
What do the server tags on Wizla's Test Server mean?
These are the tags Wizla's Test Server publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): Game build: 167231; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^c (Creative): No gathering here: it's sandbox building, so build what you want; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 Wizla's Test Server appear?
The Rust Server Trends lists that take in Wizla's Test Server are: Modded Rust servers, tracked live, Rust build and creative servers, live and Rust creative servers. You will find it under these filters on the server list: Type: Modded; Server tag: Creative ^c, Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
What steps get you onto Wizla's Test Server?
You can connect by pressing F1 in Rust and typing client.connect 84.67.167.117:28015 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.