On the class lists: F (37), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average0peak 1
Rank#9,803top 44%
No wipesresets5 new worlds this week: a reset every few hours, not a wipe schedule
Next wipe–resets, no wipes
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
30/ 100
F
A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
56/ 100
C−
Working its way up from the back of the class: #9,803 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 233 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in performance (A+); uptime 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.
AveragePeak
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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 44% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
a new world every few hours
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W·W
·W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
World resets
a new world every few hours; none of these counts as a wipe
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 21:54 UTC1d ago
–
–
–
1
Sun 25 Oct, 10:50 UTC3d ago
–
–
–
0
Sun 25 Oct, 10:35 UTC3d ago
1
–
2.5 days
0
Fri 23 Oct, 11:45 UTC5d ago
–
–
–
0
Fri 23 Oct, 11:03 UTC5d ago
0
–
2 days
0
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for MyTestServer. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 88.114.139.3:28015 is the address to use.
How dependable is MyTestServer, and is it online at the moment?
You cannot join now: MyTestServer is offline, last seen 21 hours ago. According to its reported uptime, the last restart was about 51 minutes ago. It was up 11 of 120 hours over the last 5 full days, which is 9% of the time. On 23 October 2026, Rust Server Score saw it for the first time.
Does MyTestServer perform well?
It never fell below 226 server fps in the last 48 hours, averaging 233. At its peak, it held 13,008 entities, including buildings, deployables and all else in the world. Up to 1,188 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does MyTestServer sit?
You will find MyTestServer on Rust network protocol 2635 and build 167781, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does MyTestServer reset?
No resets count as wipes on MyTestServer, because the world is remade every few hours and no schedule is kept.
Player numbers
Where does MyTestServer place in the wider field of Rust servers?
In the top 44% of all ranked servers, MyTestServer sits at #9,803 for player hours over the last seven days.
Is MyTestServer a busy server?
It has been 21 hours since MyTestServer was last seen, and it is offline right now. It peaked at 1 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 08:00 UTC, with 1 players.
Lists and filters
What is meant by the tags on MyTestServer?
You'll see MyTestServer tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is 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. 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 lists and filters on Rust Server Score show MyTestServer?
Rust Server Score lists that include MyTestServer: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Server rules
How is MyTestServer set up, and what rules does it keep?
You will find no gather rate in the name of MyTestServer. 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
MyTestServer runs which map?
The game generates the procedural map on MyTestServer at size 2,000 with seed 1337. 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 MyTestServer?
Enter client.connect 88.114.139.3:28015 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 asmp1,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is 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+); uptime is the one to work on (F).