On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,269top 68%
Last wipe27d 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 50 on average. Plenty of space to grow.
Standingrank on player hours
32/ 100
F
Working its way up from the back of the class: #15,269 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
65/ 100
C+
Slows down under load at times: 39 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
50/ 100
D
Holding steady: down 144 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 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 68% 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 peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 07:04 UTC27d ago
0
–
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
You'll find no region listed by Lexxer Map_test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 147.93.160.205:28815.
Is Lexxer Map_test up, and how steady is its uptime?
You can join now: Lexxer Map_test is online. According to its reported uptime, the last restart was about 7 days ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Is Lexxer Map_test smooth to play on?
It averaged 39 server fps over the last 48 hours, with a low of 10. At its peak, it held 68,040 entities, including buildings, deployables and all else in the world. Up to 3,966 MB of memory was used. Players feel lag when fps drops and entities pile up.
What Rust version is Lexxer Map_test on?
The server Lexxer Map_test is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Lexxer Map_test wipe, and how often?
Lexxer Map_test has not had enough wipes recorded to reveal its 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 27 days 13 hours.
What should you expect from wipe day on Lexxer Map_test?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Population
Where does Lexxer Map_test place in the wider field of Rust servers?
In the top 68% of all ranked servers, Lexxer Map_test sits at #15,269 for player hours over the last seven days.
What does the population on Lexxer Map_test look like?
With 50 slots available, Lexxer Map_test currently has 0 players. Over the past seven days, the average player count was 0.
Tags and filters
What is meant by the tags on Lexxer Map_test?
You'll see Lexxer Map_test tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^q (Premium): Joining requires premium status on Rust; ^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 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 lists and filters on Rust Server Score show Lexxer Map_test?
These Rust Server Score lists count Lexxer Map_test among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is Lexxer Map_test set up, and what rules does it keep?
The name of Lexxer Map_test gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. Joining requires premium status on Rust. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Lexxer Map_test uses?
The game generates the procedural map on Lexxer Map_test at size 4,250 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
Connecting
How should you connect to Lexxer Map_test?
To connect, start Rust, press F1, and type client.connect 147.93.160.205:28815. Or click Launch Rust here, which launches Rust through Steam and joins you. Joining requires premium status on Rust.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,^q,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^q
PremiumJoining requires premium status on Rust.
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it 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 uptime (A+); population is the one to work on (F).