On the class lists: C+ (68), with population over 48 hours and no performance mark.
Players now0/ 2500% full
7-day average1peak 6
Rank#3,119top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 13hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 1 of 250 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,119 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 80 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 336 places this week.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
daily · 1 is best
RankRank in region
Top 14% of all ranked servers, and #234 of the trio servers (top 37%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···WW··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 13h.
The force wipe · high confidence
usual gap6.4 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
8d 13hThu 5 Nov, 19:00 UTCFW
9d 11hFri 6 Nov, 16:54 UTC
23d 11hFri 20 Nov, 16:54 UTC
36d 13hThu 3 Dec, 19:00 UTCFW
37d 11hFri 4 Dec, 16:54 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 6, 40 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 16:54 UTC4d ago
6
–
running
0
Fri 16 Oct, 15:22 UTC11d ago
3
✓ held half
7.1 days
1
Thu 15 Oct, 09:09 UTC12d ago
3
–
1.3 days
0
Thu 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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS based in?
No region is published for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 46.174.55.78:28015.
How reliable is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, and is it up?
You can join now: KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is online. According to its reported uptime, the last restart was about 1 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 8 October 2026.
How well does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run?
The average over the last 48 hours was 80 server fps, and it never went below 60. Buildings, deployables and everything else in the world added up to as many as 144,029 entities. Memory use reached up to 6,373 MB. Players feel lag when fps drops and entities pile up.
What Rust version is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS on?
You will find KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS reset?
The prediction follows its tag, because too few of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's wipes are on record to confirm the schedule. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 4 days 12 hours. Its tags say it wipes every two weeks.
What should you expect from wipe day on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
The average peak on its recent wipes was 4 players. 40 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player count
Where does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS place in the wider field of Rust servers?
Over the last seven days, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS has #3,119 for player hours, in the top 14% of all ranked servers. In the trio group, it ranks #234.
How many players does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS usually have?
With 250 slots available, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS currently has 0 players. It peaked at 6 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 16:00 UTC, with an average of 3 players.
Tags and filters
What is meant by the tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
You'll see KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp250 (Max players): 250 slots are available; ts3 (Group limit): A team can hold 3 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; jp0 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one; oxidation (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Rust Server Score lists that include KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 2x Rust servers, graded, Modded Rust servers, graded, Rust combat training servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: 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.
Rules and settings
What settings and rules apply on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Going by its name, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs 2x gather. You can have up to 3 players in a group (trio). survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
The game generates the procedural map on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at size 4,500 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
Getting in
How should you connect to KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?
Enter client.connect 46.174.55.78:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://kaiman12rus.ru.
Server tags
what each one means
Published asmp250,ptrak,jp0,$r?,v2635,^b,gmrust,cs168909,ts3,^o^z,oxidation
Game
gmrust
Game modeRust survival, played by the standard rules.
mp250
Max players250 slots are available.
ts3
Group limitA team can hold 3 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
jp0
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
oxidation
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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.
A steady term. Strongest in performance (A+); population is the one to work on (F).