On the class lists: F (37), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average0peak 1
Rank#14,698top 66% · #495 in EA
Last wipe4d agoweekly schedule
Next wipe2d 11hFri 30 Oct, 09:25 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 150 on average. Plenty of space to grow.
Standingrank on player hours
34/ 100
F
Working its way up from the back of the class: #14,698 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
78/ 100
B
Mostly smooth: 47 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 532 places this week.
A term to build on.
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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 66% of all ranked servers, top 90% in EA, and #506 of the trio servers (top 80%). Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
····W··
·······
·······
····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 Friday 30 October, 09:25 UTC, in 2d 11h.
Its weekly schedule tag · low confidence
usual gap14.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5
Coming wipes
2d 11hFri 30 Oct, 09:25 UTC
8d 20hThu 5 Nov, 19:00 UTCFW
9d 11hFri 6 Nov, 09:25 UTC
16d 11hFri 13 Nov, 09:25 UTC
23d 11hFri 20 Nov, 09:25 UTC
30d 11hFri 27 Nov, 09:25 UTC
36d 20hThu 3 Dec, 19:00 UTCFW
37d 11hFri 4 Dec, 09:25 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 2 OctThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 09:25 UTC4d ago
1
–
running
0
Fri 2 Oct, 19:26 UTC25d ago
1
halved by day 2
20.6 days
0
Thu 24 Sep, 14:15 UTC33d ago
2
halved by day 3
8.2 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 [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours sit?
The EA tag on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours puts it in Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 167.104.102.100:28015 is the address to use.
How dependable is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours, and is it online at the moment?
You can join now: [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is online. The uptime it reports puts the last restart at about 4 minutes ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. On 20 September 2026, Rust Server Score saw it for the first time.
It averaged 47 server fps over the last 48 hours, with a low of 12. At its peak, it held 66,918 entities, including buildings, deployables and all else in the world. Up to 2,335 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on?
You will find [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours reset?
Its tag sets the prediction, as the record holds too few of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's wipes to confirm its schedule. It is due to wipe next on Friday 30 October at 09:25 UTC. It has been running its current world for 4 days 12 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
The average peak on its recent wipes was 1 players. 5 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 2.5 in the wipes where it did not hold.
Player numbers
Where does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours place in the wider field of Rust servers?
In Asia, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours is #495, and overall it is #14,698 on player hours over the last seven days, in the top 66% of all ranked servers. In the trio group, it ranks #506.
Is [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours a busy server?
With 150 slots available, [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours currently has 0 players. Averaging 0 players over seven days, it peaked at 1.
Tags and filters
What do [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 slots are available; ts3 (Group limit): No team may go above 3; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): The server browser lists it under East Asia are the tags [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
These Rust Server Score lists count [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Server rules
Which rules does [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours enforce, and what are its settings?
The name of [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours points to a 2x gather rate. The cap on group size is 3 players (trio). You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours uses?
[SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours runs a game-generated procedural map at size 3,500, seed 272704469. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to [SEA] AsiaForMe | 2x Vanilla+ | MAX3 | Raid Hours?
Enter client.connect 167.104.102.100:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/6DAQjtGZD6.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp150
Max players150 slots are available.
ts3
Group limitNo team may go above 3.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaThe server browser lists it under East Asia.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).