１１１
Offline 157.85.88.87:28075 checked 12h ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 12:35 UTC20h ago | – | – | running | 1 |
| Sat 24 Oct, 13:12 UTC3d ago | 1 | held half | 3 days | 0 |
| Mon 19 Oct, 16:40 UTC8d ago | 1 | held half | 4.9 days | 1 |
| Fri 16 Oct, 17:24 UTC11d ago | 1 | held half | 3 days | 1 |
| Thu 8 Oct, 14:21 UTC19d ago | 1 | held half | 8.1 days | 1 |
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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 155 on average | 155 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 182 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 95 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 40 / 1000 |
Quick answers
from the figures on this pageWipe data
On what cycle does １１１ wipe?
With irregular wipe times, １１１ offers no next wipe to predict. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 20 hours ago the current world was made.
Wipe day on １１１: what should you expect?
The average busiest count over recent wipes is 1 players. The highest player count on the latest wipe arrived 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server
What is the hosting location of １１１?
No region appears in what １１１ publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 157.85.88.87:28075.
What Rust build does １１１ run?
On Linux, １１１ runs Rust network protocol 2635 and build 168909. The protocol has to match before you can join; Steam updates it automatically.
How reliable is １１１, and is it online now?
Offline at this refresh: １１１, last seen 12 hours ago. The uptime it reports puts the last restart at about 2 hours ago. 54% uptime over the last 7 full days, equal to 90 of 168 hours. The first sighting of it by Rust Server Analytics was on 3 October 2026.
What performance does １１１ show?
Server fps averaged 238 over the last 48 hours, with a floor of 227. Entity count reached 47,493, covering buildings, deployables and the rest of the world. Peak memory was 3,520 MB. A climbing entity count and low fps are the lag players perceive.
Lists and tags
What do １１１'s tags stand for?
gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): Capacity of 1 slots; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play are the tags １１１ publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does １１１ appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists １１１ fits are: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Population
Against other Rust servers, how does １１１ compare?
Player hours for the last seven days place １１１ at #4,778, in the top 21% of the ranked field.
At what level does １１１ run its population?
No response from １１１ at the latest check, with a last sighting 12 hours ago. Seven-day figures: an average of 1 players and a peak of 1. Across the last 48 hours, 11:00 UTC shows the highest average: 1 players.
Map and rules
What settings and rules does １１１ use?
Gather rate is not mentioned in the name of １１１. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Plugins or settings modify the game, and it is listed as Modded. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, enabled.
The map on １１１: which one is it?
１１１ uses a procedural map of size 3,000 with seed 1413963070, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
How to join
How do you connect to １１１?
In the Rust console (F1), enter client.connect 157.85.88.87:28075. Launch Rust on this page also works, opening Rust through Steam and connecting you.