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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S5278-02 · Sheet 2 of 10
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-S5278-03 · Sheet 3 of 10
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 gap2.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Mon 26 OctThu 22 OctSun 18 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, 4 hours in, with 1 in the queue.
ScheduleExpected wipesRG-S5278-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 01:52 UTC3d ago
1+1 queue
–
running
0
Thu 22 Oct, 03:48 UTC7d ago
0
–
3.9 days
0
Sun 18 Oct, 08:49 UTC11d ago
0
–
3.8 days
0
Tue 13 Oct, 15:30 UTC15d ago
0
–
4.7 days
0
Sat 10 Oct, 04:04 UTC19d ago
0
–
3.5 days
0
Fri 9 Oct, 10:12 UTC20d ago
0
–
0.7 days
0
Thu 8 Oct, 11:01 UTC21d ago
0
–
1 days
0
Wed 7 Oct, 12:28 UTC21d ago
1
–
0.9 days
1
Mon 5 Oct, 12:18 UTC23d ago
1
held half
2 days
0
Sun 4 Oct, 16:12 UTC24d ago
1
–
0.8 days
1
Fri 2 Oct, 10:16 UTC27d ago
1+1 queue
held half
2.2 days
1
Wed 30 Sep, 14:14 UTC28d ago
1+1 queue
–
1.8 days
1
Mon 28 Sep, 07:57 UTC31d ago
1
held half
2.3 days
1
Fri 25 Sep, 14:20 UTC33d ago
1
–
2.7 days
0
Thu 24 Sep, 07:41 UTC35d ago
1
–
1.3 days
0
Tue 22 Sep, 12:44 UTC36d ago
1
–
1.8 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-S5278-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Right now, ТЕСТ is recorded as online. The uptime it reports puts the last restart at about 7 hours ago. 44 of 168 hours up over the last 7 full days, which is 26% of the time. On 21 September 2026 is when Rust Graphs first saw it.
2.
Is ТЕСТ stable in the figures recorded?
The last 48 hours give an average of 158 server fps and a floor of 110. Counted at its highest: 117,938 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,781 MB. What players feel as lag is low fps together with a climbing entity count.
3.
What location is recorded for ТЕСТ?
No region tag is published by ТЕСТ, but its name points to Europe. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 95.189.108.10:28015.
4.
On which Rust version is ТЕСТ running?
On Windows, ТЕСТ runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.
Player data
5.
What does the population history show for ТЕСТ?
Current player count on ТЕСТ: 1. Averaged across seven days, the player count is 1, with a peak of 1. Averaged over the last 48 hours, the player count is highest at 12:00 UTC: 1 players.
6.
Against other Rust servers, where is ТЕСТ placed?
Within the top 24% of all ranked servers: ТЕСТ at #5,278 for player hours, seven days recorded.
Wipe data
7.
What happens on ТЕСТ on the day of a wipe?
The recent wipes averaged a busiest count of 0 players. With 1 more waiting in the queue, the crowd on the latest wipe peaked 4 hours after the wipe.
8.
On ТЕСТ, when do wipes occur?
No next wipe can be predicted for ТЕСТ: its wipes fall at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 3 days 6 hours ago.
Map and rules
9.
Which rules and settings are recorded for ТЕСТ?
No gather rate is stated in the name of ТЕСТ. The group limit is 8 players, the game's default. 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 Oxide. Anti-cheat: VAC, from Valve, is on.
10.
On which map is ТЕСТ played?
Size 4,250 with seed 62340382: that is the procedural map ТЕСТ runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Lists and filters
11.
Where does ТЕСТ appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry ТЕСТ are: Europe servers, plotted and Modded Rust servers. On the server list, these filters bring it up: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
12.
Which meaning is attached to each tag on ТЕСТ?
Tags published by ТЕСТ, and read by the game's server browser: gmvanilla (Game mode): Survival, vanilla style; mp0 (Max players): Slots: 0; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
13.
By what method do you join ТЕСТ?
Connect with client.connect 95.189.108.10:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
NotesAnswered from the figuresRG-S5278-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp0
Max playersSlots: 0.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is 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.