A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
32/ 100
F
Working its way up from the back of the class: #15,269 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
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 68% 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
Mi Servidor Solo leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 191.82.245.144:28015 is the address to use.
How reliable is Mi Servidor Solo, and is it up?
At this moment, Mi Servidor Solo is offline; the last time it was seen was 45 hours ago. It was up 2% of the time over the last 2 full days, 1 of 48 hours. The first sighting by Rust Server Score was on 26 October 2026.
On what Rust version does Mi Servidor Solo sit?
The server Mi Servidor Solo is on Rust network protocol 2634 and build 167398 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Mi Servidor Solo wipe, and how often?
The record holds too few of Mi Servidor Solo's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 17 days 13 hours.
Player count
What position does Mi Servidor Solo hold in the rankings?
In the top 68% of all ranked servers, Mi Servidor Solo sits at #15,269 for player hours over the last seven days.
Is Mi Servidor Solo a busy server?
It has been 45 hours since Mi Servidor Solo was last seen, and it is offline right now. A seven-day average of 0 players applies here.
Tags
How should you read the tags on Mi Servidor Solo?
You'll see Mi Servidor Solo tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): The game build is 167398; 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 Mi Servidor Solo?
Rust Server Score lists that include Mi Servidor Solo: 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
How is Mi Servidor Solo set up, and what rules does it keep?
The name of Mi Servidor Solo gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Mi Servidor Solo runs which map?
A procedural map, generated by the game, is what Mi Servidor Solo runs.
How to join
How should you connect to Mi Servidor Solo?
To connect, start Rust, press F1, and type client.connect 191.82.245.144:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThe game build is 167398.
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 standing (F); population is the one to work on (F).