On the class lists: F (37), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 3
Rank#5,505top 25%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
75/ 100
B
Holds a respectable place: #5,505 on player hours.
Uptimehours on the list, last 48
38/ 100
F
Attendance needs work: on the list only 18 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 162 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 399 places this week. Nothing a good wipe can't fix.
A term to build on.
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
No five-minute samples in the last two hours.
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 19 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W···W··
····W··
····W··
W···W··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap5.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held25%else halves by day 2
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctMon 12 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 19:20 UTC4d ago
3
–
running
1
Fri 16 Oct, 19:38 UTC11d ago
5
halved by day 2
7 days
4
Mon 12 Oct, 18:31 UTC15d ago
3
halved by day 2
4 days
0
Fri 9 Oct, 20:44 UTC18d ago
3
✓ held half
2.9 days
0
Fri 2 Oct, 10:58 UTC25d ago
0
–
7.4 days
0
Fri 25 Sep, 12:10 UTC32d ago
1
halved by day 4
6.9 days
0
Mon 21 Sep, 14:30 UTC36d ago
4
halved by day 2
3.9 days
1
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
EU · groups of 300+ · 2x · weekly · 298 on average
78 / 1000
Quick answers
from the figures on this page
About the server
In what location does InvokeRust WEX [X2, Vanilla, No Limit] sit?
InvokeRust WEX [X2, Vanilla, No Limit] leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 109.248.4.20:35000.
How reliable is InvokeRust WEX [X2, Vanilla, No Limit], and is it up?
The server is down: InvokeRust WEX [X2, Vanilla, No Limit] is offline now, with the last sighting 30 hours ago. About 3 days ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 142 of 168 hours, or 85% of the time. It was first seen by Rust Server Score on 19 September 2026.
How well does InvokeRust WEX [X2, Vanilla, No Limit] run?
It averaged 162 server fps over the last 48 hours, with a low of 103. Buildings, deployables and everything else in the world added up to as many as 68,647 entities. At its highest, it used 2,913 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is InvokeRust WEX [X2, Vanilla, No Limit] on?
You will find InvokeRust WEX [X2, Vanilla, No Limit] on Rust network protocol 2635 and build 167398, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does InvokeRust WEX [X2, Vanilla, No Limit] wipe its map?
InvokeRust WEX [X2, Vanilla, No Limit] wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 4 days 8 hours.
What happens on InvokeRust WEX [X2, Vanilla, No Limit] when wipe day arrives?
Recent wipes have peaked at 4 players on average. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 25% of its recent wipes. In the other wipes it slipped under half by day 2.
Player count
Where does InvokeRust WEX [X2, Vanilla, No Limit] place in the wider field of Rust servers?
Over the last seven days, InvokeRust WEX [X2, Vanilla, No Limit] has #5,505 for player hours, in the top 25% of all ranked servers.
What does the population on InvokeRust WEX [X2, Vanilla, No Limit] look like?
It has been 30 hours since InvokeRust WEX [X2, Vanilla, No Limit] was last seen, and it is offline right now. The seven-day average is 0 players, with a peak of 3. The highest average in the last 48 hours came at 11:00 UTC, with 1 players.
Tags
How should you read the tags on InvokeRust WEX [X2, Vanilla, No Limit]?
You'll see InvokeRust WEX [X2, Vanilla, No Limit] tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs167398 (Build): The game build is 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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.
Where does InvokeRust WEX [X2, Vanilla, No Limit] appear in the Rust Server Score lists and filters?
These Rust Server Score lists count InvokeRust WEX [X2, Vanilla, No Limit] among them: 2x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.
Server rules
How is InvokeRust WEX [X2, Vanilla, No Limit] set up, and what rules does it keep?
Going by its name, InvokeRust WEX [X2, Vanilla, No Limit] runs 2x gather. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
InvokeRust WEX [X2, Vanilla, No Limit] runs which map?
InvokeRust WEX [X2, Vanilla, No Limit] runs a game-generated procedural map at size 3,500, seed 1622660352. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to InvokeRust WEX [X2, Vanilla, No Limit]?
Enter client.connect 109.248.4.20:35000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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 term to build on. Strongest in performance (A+); population is the one to work on (F).