On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 4
Rank#3,242top 15%
Last wipe6d agoweekly schedule
Next wipe17hThu 29 Oct, 23:32 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
85/ 100
A−
Holds a respectable place: #3,242 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
75/ 100
B
Mostly smooth: 45 server fps on average.
Wipeskeeping the crowd after a wipe
20/ 100
F
Needs to keep more players after wipe day: 20% of wipes kept half their crowd.
Momentumrank now against a week ago
73/ 100
B−
Climbing fast: up 1,522 places this week.
A fair term, with more to come.
Strongest in uptime (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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 15% of all ranked servers, and #239 of the trio servers (top 38%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
···W···
···W···
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Thursday 29 October, 23:32 UTC, in 17h.
Every Thursday at 23:32 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held20%else halves by day 2.5
Coming wipes
17hThu 29 Oct, 23:32 UTC
7d 13hThu 5 Nov, 19:00 UTCFW
14d 17hThu 12 Nov, 23:32 UTC
21d 17hThu 19 Nov, 23:32 UTC
28d 17hThu 26 Nov, 23:32 UTC
35d 13hThu 3 Dec, 19:00 UTCFW
42d 17hThu 10 Dec, 23:32 UTC
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 38 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 23:32 UTC6d ago
4
–
running
0
Thu 15 Oct, 23:33 UTC13d ago
2
✓ held half
7 days
0
Thu 8 Oct, 23:32 UTC20d ago
3
halved by day 2
7 days
0
Thu 1 Oct, 23:32 UTCFW27d ago
5
halved by day 4
7 days
0
Thu 24 Sep, 23:32 UTC34d ago
5
halved by day 3
7 days
0
Thu 17 Sep, 23:32 UTC41d ago
8
halved by day 2
7 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
In what location does MAX3|x2|Kits|TP|Vip[Viking] sit?
No region is published for MAX3|x2|Kits|TP|Vip[Viking]. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 78.29.14.210:28215 is the address to use.
Is MAX3|x2|Kits|TP|Vip[Viking] up, and how steady is its uptime?
You can join now: MAX3|x2|Kits|TP|Vip[Viking] is online. About 4 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does MAX3|x2|Kits|TP|Vip[Viking] run?
It never fell below 10 server fps in the last 48 hours, averaging 45. At its peak, it held 102,726 entities, including buildings, deployables and all else in the world. At its highest, it used 3,441 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is MAX3|x2|Kits|TP|Vip[Viking] running?
You will find MAX3|x2|Kits|TP|Vip[Viking] 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 schedule
How frequently does MAX3|x2|Kits|TP|Vip[Viking] wipe its map?
Its wipe pattern: MAX3|x2|Kits|TP|Vip[Viking] wipes every Thursday at 23:32 UTC. Thursday 29 October at 23:32 UTC is the date set for its next wipe. 6 days 6 hours have passed since this world was made. The tags carry a weekly wipe schedule.
What happens on MAX3|x2|Kits|TP|Vip[Viking] when wipe day arrives?
Recent wipes have peaked at 3 players on average. Peak numbers came 38 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 20% of its recent wipes. Day 2.5 is when it sank below half in the wipes that did not hold.
Player numbers
What position does MAX3|x2|Kits|TP|Vip[Viking] hold in the rankings?
In the top 15% of all ranked servers, MAX3|x2|Kits|TP|Vip[Viking] sits at #3,242 for player hours over the last seven days. It comes #239 among servers in the trio group.
Is MAX3|x2|Kits|TP|Vip[Viking] a busy server?
MAX3|x2|Kits|TP|Vip[Viking] is showing 0 players right now, with 100 slots in total. The seven-day average is 1 players, with a peak of 4. The busiest time in the last 48 hours was 12:00 UTC, with an average of 2 players.
Lists and filters
What is meant by the tags on MAX3|x2|Kits|TP|Vip[Viking]?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): No team may go above 3; 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): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags MAX3|x2|Kits|TP|Vip[Viking] publishes, and the game's server browser reads them. 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 MAX3|x2|Kits|TP|Vip[Viking]?
These Rust Server Score lists count MAX3|x2|Kits|TP|Vip[Viking] among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Server rules
What settings and rules apply on MAX3|x2|Kits|TP|Vip[Viking]?
Going by its name, MAX3|x2|Kits|TP|Vip[Viking] runs 2x gather. The cap on group size is 3 players (trio). survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map MAX3|x2|Kits|TP|Vip[Viking] uses?
A procedural map of size 4,000 and seed 1593250117, generated by the game, is what MAX3|x2|Kits|TP|Vip[Viking] runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto MAX3|x2|Kits|TP|Vip[Viking]?
To connect, start Rust, press F1, and type client.connect 78.29.14.210:28215. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at http://viking.gamestores.app/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts3
Group limitNo team may go above 3.
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 codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).