On the class lists: D (49), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#12,882top 58%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
42/ 100
F
Working its way up from the back of the class: #12,882 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
100/ 100
A+
Runs smoothly: 215 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
59/ 100
C−
Moving up: up 2,291 places this week.
A fair term, with more to come.
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 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 58% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 21 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 00:16 UTC25d ago
1
–
running
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
No region is published for We Love Rust | PvE |. Rust Server Score takes the server's word for its location and does not trace the hardware. 192.34.101.99:50000 is the address to use.
How dependable is We Love Rust | PvE |, and is it online at the moment?
The server is up: We Love Rust | PvE | is online now. The uptime it reports puts the last restart at about 16 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does We Love Rust | PvE | perform well?
It averaged 215 server fps over the last 48 hours, with a low of 160. At its peak, it held 71,706 entities, including buildings, deployables and all else in the world. At its highest, it used 2,516 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is We Love Rust | PvE | on?
Rust network protocol 2635 and build 168909 on Linux is what We Love Rust | PvE | runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does We Love Rust | PvE | wipe its map?
There are too few wipes on record for We Love Rust | PvE | to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 25 days 18 hours.
What happens on We Love Rust | PvE | when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 21 hours after it began.
Player count
Where does We Love Rust | PvE | place in the wider field of Rust servers?
In the top 58% of all ranked servers, We Love Rust | PvE | sits at #12,882 for player hours over the last seven days.
What does the population on We Love Rust | PvE | look like?
Right now, 0 players are on We Love Rust | PvE |, which has 100 slots. It peaked at 1 and averaged 0 players over the last seven days.
Tags and filters
What is meant by the tags on We Love Rust | PvE |?
The game's browser takes its cue from the tags We Love Rust | PvE | has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature We Love Rust | PvE |?
These Rust Server Score lists count We Love Rust | PvE | among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does We Love Rust | PvE | enforce, and what are its settings?
Nothing in the name of We Love Rust | PvE | states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on We Love Rust | PvE |?
We Love Rust | PvE | runs a game-generated procedural map at size 3,500, seed 379859120. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join We Love Rust | PvE |?
Enter client.connect 192.34.101.99:50000 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://discord.com/invite/5WcNFbPA.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).