Working its way up from the back of the class: #16,013 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 884 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
In what location does [EC] Mi Servidor Optimizado | Max 10 sit?
No region is published for [EC] Mi Servidor Optimizado | Max 10. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 157.100.136.172:28015.
Is [EC] Mi Servidor Optimizado | Max 10 up, and how steady is its uptime?
The server is down: [EC] Mi Servidor Optimizado | Max 10 is offline now, with the last sighting 24 days 5 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 3 October 2026.
On what Rust version does [EC] Mi Servidor Optimizado | Max 10 sit?
The server [EC] Mi Servidor Optimizado | Max 10 is on Rust network protocol 2631 and build 156658 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [EC] Mi Servidor Optimizado | Max 10 reset?
[EC] Mi Servidor Optimizado | Max 10 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 115 days 22 hours.
Player count
Where does [EC] Mi Servidor Optimizado | Max 10 place in the wider field of Rust servers?
In the top 70% of all ranked servers, [EC] Mi Servidor Optimizado | Max 10 sits at #16,013 for player hours over the last seven days.
Is [EC] Mi Servidor Optimizado | Max 10 a busy server?
It has been 24 days 5 hours since [EC] Mi Servidor Optimizado | Max 10 was last seen, and it is offline right now.
Lists and filters
How should you read the tags on [EC] Mi Servidor Optimizado | Max 10?
You'll see [EC] Mi Servidor Optimizado | Max 10 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs156658 (Build): This runs on build 156658; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [EC] Mi Servidor Optimizado | Max 10?
These Rust Server Score lists count [EC] Mi Servidor Optimizado | Max 10 among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does [EC] Mi Servidor Optimizado | Max 10 enforce, and what are its settings?
Nothing in the name of [EC] Mi Servidor Optimizado | Max 10 states a 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. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
[EC] Mi Servidor Optimizado | Max 10 runs which map?
A procedural map, generated by the game, is what [EC] Mi Servidor Optimizado | Max 10 runs.
How to join
How should you connect to [EC] Mi Servidor Optimizado | Max 10?
Enter client.connect 157.100.136.172:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2631,gmrust,cs156658,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs156658
BuildThis runs on build 156658.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).