KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS
Online 46.174.55.78:28015 checked 17m 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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 14% of all ranked servers, and #233 of the trio servers (top 37%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence
- usual gap
- 6.4 daysbetween real wipes
- on rhythm
- 67%of its recent wipes
- wipe-day peak
- 4players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
Coming wipes
- in 8d 15hThu 5 Nov, 19:00 UTCFW
- in 9d 13hFri 6 Nov, 16:54 UTC
- in 23d 13hFri 20 Nov, 16:54 UTC
- in 36d 15hThu 3 Dec, 19:00 UTCFW
- in 37d 13hFri 4 Dec, 16:54 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 40 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
23 OCT 2026Fri 23 Oct, 16:54 UTC4d ago |
6 | – | running | 0 |
16 OCT 2026Fri 16 Oct, 15:22 UTC11d ago |
3 | held half | 7.1 days | 1 |
15 OCT 2026Thu 15 Oct, 09:09 UTC12d ago |
3 | – | 1.3 days | 0 |
8 OCT 2026Thu 8 Oct, 23:23 UTC19d ago |
3 | held half | 6.4 days | 0 |
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.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS sets gather at 2x, as its name shows. A maximum of 3 players per group applies (trio). Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. Plugins or settings change the game; it is listed under Modded in the server browser. Plugins in use: Oxide. The server has VAC, Valve's anti-cheat, turned on.
What is the map on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Generated by the game, the procedural map of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS has size 4,500 and seed 1337. From this page you can view the map on RustMaps; the same size and seed give the same map. The name of the map is Custom Map.
Lists and filters
Where does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS appear among the Rust Server Index lists and filters?
Filed under these Rust Server Index lists is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: Rust servers filed under 2x gather rate, Modded Rust servers, filed by play style, Aim training servers, filed and Trio servers, filed under group limit. Filed under these filters on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 2x.
What is meant by the tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Filed under these tags, as published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp250 (Max players): The queue ceiling sits at 250; ts3 (Group limit): 3 is the largest team allowed; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Plugins or changed settings put this under Modded; jp0 (Custom tag): A custom tag: set by the owner or a plugin, not by Rust itself; oxidation (Custom tag): A custom tag: set by the owner or a plugin, not by Rust itself. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe dates
What happens on wipe day at KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
The average peak across its recent wipes is 4 players. 40 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
When does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS wipe?
Too few wipes of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS are recorded to confirm its schedule, so the tag sets the prediction. Its next wipe falls on Thursday 5 November at 19:00 UTC, as the force wipe that reaches every Rust server. Its present world dates from 4 days 10 hours. A wipe schedule of every two weeks is published in its tags.
Players and ranking
How is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS ranked compared with the rest?
The seven-day player-hours ranking places KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,103, among the top 14% of ranked servers. #233 is where it sits in the trio servers.
What does the player count on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS look like?
The live count for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS stands at 0 players, out of 250 slots. Averaged across seven days: 1 players, peaking at 6. Filed under busiest hour: 16:00 UTC in the last 48 hours, averaging 3 players.
Server details
Which Rust build is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS running?
Rust network protocol 2635 and build 168909, on Linux, is what KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs. Steam keeps your game updated, but the protocol must match for you to join.
Is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS reachable, and does it stay up?
You will find KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS online as of now. The uptime it reports puts the last restart at about 10 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. The earliest sighting at Rust Server Index is 8 October 2026.
Is the performance on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS good?
The last 48 hours give an average of 80 server fps and a floor of 60. The entity count reached 144,029, covering buildings, deployables and all else in the world. Up to 6,373 MB of memory was in use. What players feel as lag is low fps together with a rising entity count.
Where in the world is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS hosted?
There is no region on record for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 46.174.55.78:28015.
Joining the server
How can you connect to KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Two ways in. Type client.connect 46.174.55.78:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. https://kaiman12rus.ru is where its website lives.
Server tags
What each one means.
Published as mp250,ptrak,jp0,$r?,v2635,^b,gmrust,cs168909,ts3,^o^z,oxidation
Game
gmrust
mp250
ts3
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Other
jp0
oxidation
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.