Fig. 1Players on SiunattuRG-S6576-01 · Sheet 1 of 10
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S6576-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S6576-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.1 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Thu 22 OctFri 16 OctTue 13 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, 4 hours in.
ScheduleExpected wipesRG-S6576-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 17:25 UTC6d ago
2
–
running
0
Fri 16 Oct, 22:39 UTC12d ago
1
halved by day 1
5.8 days
0
Tue 13 Oct, 19:45 UTC15d ago
1
halved by day 1
3.1 days
1
Sun 11 Oct, 22:23 UTC17d ago
1
–
1.9 days
1
Tue 6 Oct, 01:08 UTC23d ago
1
halved by day 2
5.9 days
1
Sun 4 Oct, 02:09 UTC24d ago
1
–
2 days
1
Thu 1 Oct, 18:54 UTCFW27d ago
1
held half
2.3 days
1
Tue 29 Sep, 21:48 UTC29d ago
1
–
1.9 days
0
Mon 28 Sep, 17:43 UTC30d ago
1
–
1.2 days
1
Fri 25 Sep, 04:57 UTC33d ago
1
halved by day 2
3.5 days
0
Sun 20 Sep, 22:50 UTC38d ago
1
held half
4.3 days
0
Thu 17 Sep, 01:42 UTC41d ago
1
halved by day 1
3.9 days
0
Tue 15 Sep, 18:34 UTC43d ago
1
–
1.3 days
1
Sun 13 Sep, 17:02 UTC45d ago
1
held half
2.1 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-S6576-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Right now, Siunattu is recorded as online. About 31 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 158 of 168 hours up, 94% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What does the recorded performance of Siunattu show?
Average server fps over the last 48 hours is 215; the lowest was 161. Counted at its highest: 50,828 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 4,035 MB. A climbing entity count and low fps are the source of what players feel as lag.
3.
In which location is Siunattu hosted?
No region is published by Siunattu. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 135.148.15.62:28015.
4.
What Rust version is recorded for Siunattu?
Rust network protocol 2635 and build 168909 on Linux: that is what Siunattu runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
What does the population history show for Siunattu?
Current player count on Siunattu: 0, of 40 slots. Averaged across seven days, the player count is 0, with a peak of 2. The 48-hour peak falls at 23:00 UTC, averaging 1 players.
6.
Against other Rust servers, where is Siunattu placed?
Within the top 30% of all ranked servers: Siunattu at #6,576 for player hours, seven days recorded.
Wipe times
7.
What happens on Siunattu on the day of a wipe?
The recent wipes averaged a busiest count of 1 players. 4 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 1 the crowd had fallen below half on the wipes where it did not hold.
8.
On Siunattu, when do wipes occur?
There is no next wipe to predict at Siunattu, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 6 days 4 hours ago the current world was made.
Map and rules
9.
What settings and rules apply on Siunattu?
The name of Siunattu records no gather rate. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. It appears under Community in the server browser. Anti-cheat: VAC, from Valve, is on.
10.
Which map has Siunattu loaded?
Seed 123457 and size 3,100 define the procedural map Siunattu generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Tags
11.
On Rust Graphs, which lists and filters contain Siunattu?
These Rust Graphs lists include Siunattu: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
12.
Which meaning is attached to each tag on Siunattu?
gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): 40 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set are the tags Siunattu publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
13.
What is the way to connect to Siunattu?
In Rust, press F1 and type client.connect 135.148.15.62:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
NotesAnswered from the figuresRG-S6576-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeStandard survival, as Rust plays.
mp40
Max players40 player slots.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeRegion code not set.
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.