Fig. 1Players on TESTERRG-S5250-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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S5250-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 24% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S5250-03 · Sheet 3 of 11
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.1 daysbetween real wipes
on rhythm14%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Mon 26 OctMon 26 OctThu 22 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-S5250-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 23:02 UTC2d ago
1
–
running
0
Mon 26 Oct, 12:27 UTC2d ago
1
–
0.4 days
1
Thu 22 Oct, 17:00 UTC6d ago
2
held half
3.8 days
2
Wed 21 Oct, 15:19 UTC7d ago
2
–
1.1 days
0
Sun 18 Oct, 11:48 UTC10d ago
1
held half
3.1 days
1
Thu 15 Oct, 21:30 UTC13d ago
1
held half
2.6 days
0
Thu 1 Oct, 10:02 UTC28d ago
1
–
14.5 days
0
Thu 24 Sep, 15:33 UTC34d ago
2
–
6.8 days
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.
Table 1Wipe logRG-S5250-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
At this moment TESTER is online. About 37 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 149 of 168 hours up, 89% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What does the recorded performance of TESTER show?
Average server fps over the last 48 hours is 406; the lowest was 232. Counted at its highest: 16,007 entities, buildings, deployables and the rest of the world included. Memory use peaked at 1,975 MB. What players feel as lag is low fps together with a climbing entity count.
3.
In which location is TESTER hosted?
A region is not published by TESTER. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 188.134.89.81:11113 is its address.
4.
On which Rust version is TESTER running?
The platform is Windows and the version is Rust network protocol 2635 and build 168909 on TESTER. The same protocol is required for joining, and Steam updates your game to it.
Population
5.
What does the population history show for TESTER?
0 of 100 slots on TESTER 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 17:00 UTC, averaging 1 players.
6.
In the rankings, which position does TESTER hold?
Over the last seven days, TESTER records #5,250 for player hours: the top 24% of all ranked servers.
Wipe times
7.
What happens on TESTER on the day of a wipe?
At their busiest, its recent wipes drew 1 players on average. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.
8.
Which times and days are wipes plotted at on TESTER?
No next wipe can be predicted for TESTER: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 2 days 11 hours ago the current world was made.
Map and rules
9.
Which settings does TESTER run, and what rules?
Gather rate for TESTER: not stated in the name. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Carbon. VAC is on: that is Valve's anti-cheat.
10.
What is the map for TESTER?
TESTER runs a procedural map of size 1,500 with seed 1724362619, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
11.
Where does TESTER appear among the Rust Graphs lists and filters?
These Rust Graphs lists include TESTER: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
12.
On TESTER, what is meant by each tag?
Tags published by TESTER, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptsw (Networking): This server runs on network layer 'sw'; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Carbon is the plugin framework here. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
13.
How is TESTER joined?
In Rust, press F1 and type client.connect 188.134.89.81:11113 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://rustila.gamestores.app.
NotesAnswered from the figuresRG-S5250-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp100,ptsw,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeStandard survival, as Rust plays.
mp100
Max playersSlots: 100.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
BuildBuild: 168909.
ptsw
NetworkingThis server runs on network layer 'sw'.
$r?
Region codeThe region code field is empty.
Mods and access
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
^y
CarbonCarbon is the plugin framework here.
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.
