Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped
Online 160.115.2.11:27131 checked 10m ago
Server instruments
last reading Thu 20:00 UTCPlayers now
61% full 7-day avg7-day peak 231, past the slotsServer fps
48 h low 158 · below 20 is lag, below 10 is badEntities
48 h range 87,176–136,083 · memory 4,789 MBUptime
4 h 34 min since its last restart, at the last readingPlayers
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 2% of all ranked servers, and #41 of the trio servers (top 7%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 6d 21h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 21hFW
- WPT 2Thu 12 Nov, 15:27 UTC13d 17h
- WPT 3Thu 19 Nov, 15:27 UTC20d 17h
- WPT 4Thu 26 Nov, 15:27 UTC27d 17h
- WPT 5Thu 3 Dec, 19:00 UTC34d 21hFW
- WPT 6Thu 10 Dec, 15:27 UTC41d 17h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 263, 2 hours in, with 58 in the queue.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 15:27 UTC6h ago | – | – | running | 102 |
| Thu 22 Oct, 15:28 UTC7d ago | 263+58 queue | – | – | 108 |
| Thu 15 Oct, 15:29 UTC14d ago | 220+47 queue | halved by day 3 | 7 days | 116 |
| Thu 8 Oct, 15:27 UTC21d ago | 270+40 queue | halved by day 3 | 7 days | 114 |
| Thu 1 Oct, 17:59 UTC FW28d ago | 168+9 queue | halved by day 4 | 6.9 days | 35 |
| Thu 24 Sep, 15:25 UTC35d ago | 316+192 queue | halved by day 3 | 7.1 days | 150 |
| Thu 17 Sep, 15:26 UTC42d ago | 302+63 queue | halved by day 3 | 7 days | 11 |
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- 1/100
- 8/500
- 649/700
- 645/675
- 33/100
- 144/300
Quick answers
from the figures on this pageWipe schedule
What happens on Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped when wipe day comes?
At their busiest, its recent wipes drew 251 players on average. With 58 more waiting in the queue, the crowd peaked 2 hours after the wipe on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 3 it fell below half when it didn't.
What wipe timing does Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped follow?
The wipe rhythm of Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped is every Thursday at 15:27 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 6 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.
Lists and filters
How should you read the tags on Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped?
These are the tags Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptnone (Networking): 'none' is the network layer in use; $raf (Region code): Region code reading: af; ^w (Weekly): Check: wipe cycle. Every week; ^z (Modded): Plugins or settings make this a modded server; rustmaps (Custom tag): This tag is non-standard, added by the owner or a plugin; stok (Custom tag): This tag is non-standard, added by the owner or a plugin. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which operator is behind Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped?
Check: operator. Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped publishes a intoxicated.games hostname, and 7 other servers we track do too. Same operator, most likely.
Where does Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. Check: filters. On the server list it appears under these: Region: Africa; Type: Modded; Server tag: Weekly ^w and Modded ^z; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 2x; Players now: At least 100; Average players: 50+ on average.
Occupancy
What position does Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped hold among Rust servers?
Player hours over seven days put Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped at #339, in the top 2% of all ranked servers. Among servers in trio, it stands at #41.
What player count does Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped carry?
Current headcount on Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped: 122 players, 200 slots available. Check: players over seven days. Average 53, peak 231. Check: 48-hour peak. 17:00 UTC, 225 players on average.
Operator and location
What location is Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped hosted in?
Reading: location. None in the tags, but the name of Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped points to Africa, with region code af. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.115.2.11:27131.
What Rust version is Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped on?
Reading: Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped?
Over the last 48 hours the average was 231 server fps; the floor was 158. Peak entity count: 136,083. Buildings, deployables and all else included. Reading: 8,562 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
How reliable is Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped, and is it online now?
Check: connection. Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped is online at this moment. Check: restart. The uptime it reports puts the last restart about 4 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped?
Gather rate check: 2x. That comes from the name Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped. The group cap is 3 players, read as trio. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Anti-cheat reading: VAC on, Valve's system.
What map is Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped on?
Size 3,800, custom map, on Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped. The file is published and downloadable here.
Join
How do you connect to Intoxicated ZA Solo/Duo/Trio 2x - 29 Oct - Just wiped?
To join: start Rust, press F1 and type client.connect 160.115.2.11:27131. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/ChTFh5w is where its website sits.