On the class lists: D (52), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 1
Rank#6,686top 30%
Last wipe11d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
70/ 100
B−
Holds a respectable place: #6,686 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
94/ 100
A
Mostly smooth: 56 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
42/ 100
F
Slipped a little: down 1,036 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in uptime (A); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
Rank
daily · 1 is best
RankRank in region
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 13:49 UTC11d ago
3
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Eto_Samoe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 91.210.106.167:28015.
How dependable is Eto_Samoe, and is it online at the moment?
The server is up: Eto_Samoe is online now. The uptime it reports puts the last restart at about 3 days 15 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does Eto_Samoe perform well?
The average over the last 48 hours was 56 server fps, and it never went below 17. At its peak, it held 121,077 entities, including buildings, deployables and all else in the world. At its highest, it used 5,253 MB of memory. Players feel lag when fps drops and entities pile up.
Which Rust version is Eto_Samoe running?
Rust network protocol 2635 and build 168909 on Linux is what Eto_Samoe runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Eto_Samoe wipe, and how often?
There are too few wipes on record for Eto_Samoe to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 11 days 6 hours.
What happens on Eto_Samoe when wipe day arrives?
Recent wipes have peaked at 3 players on average. The crowd on the latest wipe was largest 6 hours after it began.
Population
What position does Eto_Samoe hold in the rankings?
Over the last seven days, Eto_Samoe has #6,686 for player hours, in the top 30% of all ranked servers.
What does the population on Eto_Samoe look like?
With 10 slots available, Eto_Samoe currently has 0 players. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 18:00 UTC, with an average of 1 players.
Lists and filters
What is meant by the tags on Eto_Samoe?
gmvanilla (Game mode): You play vanilla survival here; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Eto_Samoe publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Eto_Samoe?
Rust Server Score lists that include Eto_Samoe: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is Eto_Samoe set up, and what rules does it keep?
The name of Eto_Samoe gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Eto_Samoe?
Eto_Samoe runs a game-generated procedural map at size 4,250, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Connecting
How should you connect to Eto_Samoe?
To connect, start Rust, press F1, and type client.connect 91.210.106.167:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.
A fair term, with more to come. Strongest in uptime (A); population is the one to work on (F).