zulabank test
Offline 31.59.131.202:28015 checked 11d ago
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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 1029/ 100
- 101/ 400
- 88/ 245
- 135/ 100
- 231/ 1000
- 18/ 700
Quick answers
Tags and listings
Where does zulabank test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include zulabank test: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on zulabank test?
gmrust (Game mode): Survival, as standard Rust does it; mp200 (Max players): It holds 200 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166652 (Build): The build number is 166652; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list zulabank test puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is zulabank test in?
No region comes from zulabank test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 31.59.131.202:28015.
What's the uptime like for zulabank test?
zulabank test is down at the moment; it was last up 11 days 7 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 6 October 2026 is when Rust Going Deep first saw it.
What Rust version is zulabank test on?
Rust network protocol 2634 and build 166652 is what zulabank test runs, on Linux. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does zulabank test follow for wipes?
Too few wipes are on record for zulabank test to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 11 days 7 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to zulabank test?
No gather rate appears in the name of zulabank test. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.
Population
Is zulabank test busy?
zulabank test was last seen 11 days 7 hours ago and is offline as you read this.
What position does zulabank test hold in the server rankings?
For player hours in the last seven days, zulabank test ranks #14,970, within the top 67% of ranked servers.
Getting in
How do you get into zulabank test?
Open Rust and press F1, then type client.connect 31.59.131.202:28015. Alternatively, click Launch Rust on this page to join via Steam.