Fig. 1Players on [GER] Rust Oase |Testserver|RG-S7153-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 29 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S7153-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 32% of all ranked servers, top 69% in EU. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S7153-03 · Sheet 3 of 11
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h.
The force wipe · high confidence
usual gap4.2 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 19hThu 5 Nov, 19:00 UTCFW
35d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctFri 16 OctThu 15 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S7153-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 16:24 UTC6d ago
1
–
running
0
Fri 16 Oct, 12:58 UTC12d ago
3
halved by day 1
6.1 days
1
Thu 15 Oct, 14:10 UTC13d ago
3
–
0.9 days
0
Wed 14 Oct, 13:46 UTC14d ago
3
–
1 days
0
Sat 3 Oct, 18:36 UTC25d ago
4
halved by day 4
10.8 days
0
Tue 29 Sep, 14:49 UTC29d ago
1
halved by day 1
4.2 days
1
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-S7153-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 [GER] Rust Oase |Testserver|, and is it up?
At this moment [GER] Rust Oase |Testserver| is online. The uptime it reports puts the last restart at about 3 days 10 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 29 September 2026.
2.
What does the recorded performance of [GER] Rust Oase |Testserver| show?
158 server fps on average over the last 48 hours, and never under 130. Counted at its highest: 48,121 entities, buildings, deployables and the rest of the world included. Memory use peaked at 5,262 MB. A climbing entity count and low fps are the source of what players feel as lag.
3.
In which location is [GER] Rust Oase |Testserver| hosted?
The EU tag is how [GER] Rust Oase |Testserver| lists itself in Europe. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 37.187.138.131:28024.
4.
What Rust version is recorded for [GER] Rust Oase |Testserver|?
On Linux, [GER] Rust Oase |Testserver| runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.
Counts
5.
What does the population history show for [GER] Rust Oase |Testserver|?
0 of 10 slots on [GER] Rust Oase |Testserver| are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 2. The 48-hour peak falls at 11:00 UTC, averaging 1 players.
6.
Against other Rust servers, where is [GER] Rust Oase |Testserver| placed?
Across seven days, player hours give [GER] Rust Oase |Testserver| #7,153 globally and #2,004 in Europe, a top 32% position among ranked servers.
Wipe times
7.
On [GER] Rust Oase |Testserver|, what does the data show for wipe day?
An average of 2 players was recorded at the busiest point of its recent wipes. At 0 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 1.
8.
Which times and days are wipes plotted at on [GER] Rust Oase |Testserver|?
The force wipe is the only wipe at [GER] Rust Oase |Testserver|, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 6 days 7 hours ago. The tags state a wipe schedule of one wipe a month.
Map and rules
9.
Which rules and settings are recorded for [GER] Rust Oase |Testserver|?
Gather rate for [GER] Rust Oase |Testserver|: not stated in the name. The group limit is 15 players. It runs the pve game mode, no fighting other players. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Carbon. Anti-cheat: VAC, from Valve, is on.
10.
What is the map for [GER] Rust Oase |Testserver|?
Seed 1026445505 and size 5,000 define the procedural map [GER] Rust Oase |Testserver| generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: 4800 Procedural Map.
Lists and filters
11.
Where does [GER] Rust Oase |Testserver| appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry [GER] Rust Oase |Testserver| are: Europe servers, plotted, Modded Rust servers and PvE Rust servers, plotted. On the server list, these filters bring it up: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
12.
On [GER] Rust Oase |Testserver|, what is meant by each tag?
The game's server browser reads these tags from [GER] Rust Oase |Testserver|: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): 10 player slots; ts15 (Group limit): Team size is capped at 15; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^p (PvE): The world is the danger; players do not fight each other; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon; EU (Europe): The browser's listing places 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.
How to join
13.
How is [GER] Rust Oase |Testserver| joined?
Enter client.connect 37.187.138.131:28024 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/4yUqwk97Ym.
NotesAnswered from the figuresRG-S7153-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,^z,^y,^m,EU,^p,gmvanilla,cs168909,ts15
Game
gmvanilla
Game modeThe mode is vanilla survival.
mp10
Max players10 player slots.
ts15
Group limitTeam size is capped at 15.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Wipe schedule
^m
MonthlyFacepunch's force wipe brings a monthly wipe.
Gameplay
^p
PvEThe world is the danger; players do not fight each other.
Mods and access
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
^y
CarbonThe plugin framework is Carbon.
Region
EU
EuropeThe browser's listing places 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.
