Fig. 1Players on MobWars Test | Dev ServerRG-S13613-01 · Sheet 1 of 11
Fig. 2
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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S13613-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers, top 84% in EU. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S13613-03 · Sheet 3 of 11
Schedule
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h.
The force wipe · high confidence
usual gap1.1 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
Coming wipes
8d 7hThu 5 Nov, 19:00 UTCFW
10d 3hSat 7 Nov, 14:40 UTC
24d 3hSat 21 Nov, 14:40 UTC
36d 7hThu 3 Dec, 19:00 UTCFW
38d 3hSat 5 Dec, 14:40 UTC
The first 48 hours of its last wipes
Sat 10 OctSat 10 OctFri 9 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
ScheduleExpected wipesRG-S13613-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 14:40 UTC17d ago
2
–
running
1
Sat 10 Oct, 08:20 UTC18d ago
2
–
0.3 days
0
Fri 9 Oct, 15:49 UTC18d ago
2
–
0.7 days
0
Sat 3 Oct, 10:17 UTC25d ago
2
halved by day 2
6.2 days
0
Wed 30 Sep, 19:08 UTC27d ago
2
–
2.6 days
2
Tue 29 Sep, 17:16 UTC28d ago
2
–
1.1 days
2
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.
Table 1Wipe logRG-S13613-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for MobWars Test | Dev Server, and is it up?
Right now, MobWars Test | Dev Server is recorded as online. About 3 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. The first sighting of it by Rust Graphs was on 18 September 2026.
2.
What does the recorded performance of MobWars Test | Dev Server show?
The last 48 hours give an average of 185 server fps and a floor of 123. Counted at its highest: 79,549 entities, buildings, deployables and the rest of the world included. 2,637 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.
3.
In which location is MobWars Test | Dev Server hosted?
With its EU tag, MobWars Test | Dev Server lists itself in Europe. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 134.255.255.19:28042.
4.
On which Rust version is MobWars Test | Dev Server running?
Rust network protocol 2635 and build 168909 on Linux: that is what MobWars Test | Dev Server runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
What player count is recorded on MobWars Test | Dev Server?
At the last refresh, MobWars Test | Dev Server recorded 0 players across 10 slots. The seven-day mean is 0 players; the peak over the same period is 1. The 48-hour peak falls at 16:00 UTC, averaging 0 players.
6.
Against other Rust servers, where is MobWars Test | Dev Server placed?
Across seven days, player hours give MobWars Test | Dev Server #13,613 globally and #2,452 in Europe, a top 61% position among ranked servers.
Wipe times
7.
What happens on MobWars Test | Dev Server on the day of a wipe?
At their busiest, its recent wipes drew 2 players on average. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. By day 2 the crowd had fallen below half on the wipes where it did not hold.
8.
What wipe schedule has been recorded for MobWars Test | Dev Server?
Too few of MobWars Test | Dev Server's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. 17 days 20 hours ago the current world was made. A wipe schedule of one wipe every two weeks is listed in its tags.
Settings
9.
Which rules and settings are recorded for MobWars Test | Dev Server?
No gather rate is stated in the name of MobWars Test | Dev Server. Eight players per group: the default for the game. It runs the pve game mode, no fighting other players. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.
10.
On which map is MobWars Test | Dev Server played?
Size 3,500 with seed 1337: that is the procedural map MobWars Test | Dev Server runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
11.
Where does MobWars Test | Dev Server appear among the Rust Graphs lists and filters?
On Rust Graphs, MobWars Test | Dev Server is placed in these lists: Europe servers, plotted, Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
12.
Which meaning is attached to each tag on MobWars Test | Dev Server?
The game's server browser reads these tags from MobWars Test | Dev Server: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; EU (Europe): The server browser lists it under Europe. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
13.
How is MobWars Test | Dev Server joined?
Connect with client.connect 134.255.255.19:28042: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://discord.com/invite/PGVAcSnxF4 is its website.
NotesAnswered from the figuresRG-S13613-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,^b,EU,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp10
Max playersThe slot count is 10.
ts8
Group limitThe team limit is 8, which is the game default.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^p
PvEThe world is the danger; players do not fight each other.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Region
EU
EuropeThe server browser lists it under Europe.
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.
KeyTag string decodedRG-S13613-11 · Sheet 11 of 11
