On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 250% full
7-day average0peak –
Rank#15,388top 70%
Last wipe25d agono schedule published
Next wipe8d 22hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 25 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,388 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: 236 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
49/ 100
D
Slipped a little: down 158 places this week. Nothing a good wipe can't fix.
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
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 70% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
8d 22hThu 5 Nov, 19:00 UTCFW
36d 22hThu 3 Dec, 19:00 UTCFW
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
Thu 1 Oct, 22:37 UTCFW25d 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
No region is published for (Wunders) Dev & Testing. Rust Server Score takes the server's word for its location and does not trace the hardware. 195.201.167.33:28025 is the address to use.
How reliable is (Wunders) Dev & Testing, and is it up?
The server is up: (Wunders) Dev & Testing is online now. According to its reported uptime, the last restart was about 2 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does (Wunders) Dev & Testing perform well?
It averaged 236 server fps over the last 48 hours, with a low of 228. Buildings, deployables and everything else in the world added up to as many as 32,953 entities. Up to 1,490 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is (Wunders) Dev & Testing running?
Rust network protocol 2635 and build 168909 on Linux is what (Wunders) Dev & Testing runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does (Wunders) Dev & Testing wipe, and how often?
The force wipe each month is the only wipe (Wunders) Dev & Testing takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 25 days 21 hours.
What should you expect from wipe day on (Wunders) Dev & Testing?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Population
Where does (Wunders) Dev & Testing sit among Rust servers?
In the top 70% of all ranked servers, (Wunders) Dev & Testing sits at #15,388 for player hours over the last seven days.
How many players does (Wunders) Dev & Testing usually have?
With 25 slots available, (Wunders) Dev & Testing currently has 0 players. A seven-day average of 0 players applies here.
Tags
What is meant by the tags on (Wunders) Dev & Testing?
The game's browser takes its cue from the tags (Wunders) Dev & Testing has set: gmrust (Game mode): Rust survival, played by the standard rules; mp25 (Max players): The server holds 25 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 (Wunders) Dev & Testing?
Rust Server Score lists that include (Wunders) Dev & Testing: 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.
Map and rules
Which rules does (Wunders) Dev & Testing enforce, and what are its settings?
You will find no gather rate in the name of (Wunders) Dev & Testing. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map (Wunders) Dev & Testing uses?
The game generates the procedural map on (Wunders) Dev & Testing at size 2,500 with seed 1234567. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to (Wunders) Dev & Testing?
To connect, start Rust, press F1, and type client.connect 195.201.167.33:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp25,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp25
Max playersThe server holds 25 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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).