On the class lists: C (61), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#5,000top 22%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
56/ 100
C−
Room for more players: 1 of 1 on average.
Standingrank on player hours
78/ 100
B
Holds a respectable place: #5,000 on player hours.
Uptimehours on the list, last 48
31/ 100
F
Attendance needs work: on the list only 15 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 237 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 404 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in performance (A+); uptime 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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
····W··
W····W·
·W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sat 24 OctMon 19 OctFri 16 Oct
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 UTC1d ago
–
–
running
1
Sat 24 Oct, 13:12 UTC4d ago
1
✓ held half
3 days
0
Mon 19 Oct, 16:40 UTC9d ago
1
✓ held half
4.9 days
1
Fri 16 Oct, 17:24 UTC12d ago
1
✓ held half
3 days
1
Thu 8 Oct, 14:21 UTC20d 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
classmates: the same kind of game, then region, group limit, rate and wipes
１１１ leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 157.85.88.87:28075.
How dependable is １１１, and is it online at the moment?
You cannot join now: １１１ is offline, last seen 29 hours ago. About 2 hours ago, it restarted, based on the uptime it reports. It was up 80 of 168 hours over the last 7 full days, which is 48% of the time. The first sighting by Rust Server Score was on 3 October 2026.
Does １１１ perform well?
The average over the last 48 hours was 237 server fps, and it never went below 227. At its peak, it held 47,427 entities, including buildings, deployables and all else in the world. At its highest, it used 3,520 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is １１１ on?
Rust network protocol 2635 and build 168909 on Linux is what １１１ runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does １１１ reset?
There is no next wipe to predict on １１１, as it wipes at irregular times. 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 38 hours.
What happens on １１１ when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 100% of its recent wipes.
Player numbers
What position does １１１ hold in the rankings?
In the top 22% of all ranked servers, １１１ sits at #5,000 for player hours over the last seven days.
Is １１１ a busy server?
１１１ is offline at the moment; the last time it was seen was 29 hours ago. It peaked at 1 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 12:00 UTC, with 1 players.
Tags and filters
What do １１１'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): 1 slots are available; 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): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags １１１ publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does １１１ appear in the Rust Server Score lists and filters?
These Rust Server Score lists count １１１ among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
Which rules does １１１ enforce, and what are its settings?
Nothing in the name of １１１ states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
１１１ runs which map?
The game generates the procedural map on １１１ at size 3,000 with seed 1413963070. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join １１１?
Enter client.connect 157.85.88.87:28075 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 asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max players1 slots are available.
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
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 steady term. Strongest in performance (A+); uptime is the one to work on (F).