Live coverage · Rust server
Offline MiServidorSoloTest is not on the server list right now. The figures below are from when it was last seen, 12d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · 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.
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
The current map
Friday 16 October 2026, 02:34 UTC
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.
At their busiest, its recent wipes averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Too few wipes are recorded for MiServidorSoloTest to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 13 days 4 hours.
These are the Rust Live Stats lists MiServidorSoloTest fits: Live Rust community servers. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
gmrust (Game mode): Standard survival, in the Rust style; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): The server runs protocol 2634, so match that version to join; cs167781 (Build): Build: 167781; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): Region code: none set: that is the tag list MiServidorSoloTest publishes for the game's server browser. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
MiServidorSoloTest is not online at the moment, having last been seen 12 days ago.
Ranked by seven-day player hours, MiServidorSoloTest is #14,662, placing it in the top 67% of ranked servers.
No gather rate appears in the name MiServidorSoloTest. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. You find it under Community in the server browser. Anti-cheat: VAC from Valve is enabled.
A procedural map, generated by the game, runs on MiServidorSoloTest.
There is no region from MiServidorSoloTest. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 138.84.41.111:28015 is its address.
Rust network protocol 2634 and build 167781 on Windows is what MiServidorSoloTest runs. Joining requires the same protocol on your game; Steam takes care of updating it.
At the time of this update, MiServidorSoloTest is down, last seen 12 days ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. On 15 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 138.84.41.111:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.