Rust Data

rustdata.spaceservers157.85.88.87:28076.ipynb

Run all rust-data · live

‹ All servers

Offline 157.85.88.87:28075 checked 4h ago

111

moddedoxide

Connect

srv = rust.server("157.85.88.87:28076")
print(srv.connect_command)

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 1 # peak 1
rank #4,750 # top 21%
last wipe 13h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75110:0017:0023:0005:0012:0021:00Wiped Tue 27 Oct, 12:35 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040010:0017:0023:0005:0012:0021:00Wiped Tue 27 Oct, 12:35 UTCWIPE

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12.5k5k7.5k10k3 Oct8 Oct13 Oct18 Oct23 Oct28 Oct

Top 21% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 12:35 UTC13h ago NaN NaN running 1
1 Sat 24 Oct, 13:12 UTC3d ago 1 held half 3 days 0
2 Mon 19 Oct, 16:40 UTC8d ago 1 held half 4.9 days 1
3 Fri 16 Oct, 17:24 UTC11d ago 1 held half 3 days 1
4 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.

display(srv.map, srv.info())

Map

3000 · seed 1413963070
Map of 111
map
Procedural Map
size
3000
seed
1413963070
Open on RustMaps

Server

srv.info()
address
157.85.88.87:28075
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 12:35 UTC
hostname
–
first seen
3 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 161 on average32/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average39/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average7/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average9/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average2/1000

Quick answers

From the figures on this page.

Population data

What position does 111 take in the server rankings?

Over the last seven days 111 sits at #4,750 on player hours, in the top 21% of ranked servers.

How full does 111 run?

111 returns no live count at this refresh, having last been seen 4 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 11:00 UTC is the busiest, at 1 players.

Server facts

How smoothly does 111 run?

Averaged over 48 hours: 238 server fps, never under 227. The entity count peaked at 47,493, covering buildings, deployables and the rest of the world. Memory peaked at 3,520 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is 111 on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by 111. Joining needs the same protocol on your game; Steam handles the update.

Is 111 up, and what does its uptime show?

The latest sample has 111 offline, with a last sighting 4 hours ago. The uptime it reports puts the last restart about 2 hours ago. Uptime of 54% across the last 7 full days: 90 hours of 168. Rust Data logged it first on 3 October 2026.

Where does 111 sit?

No region is published by 111. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 157.85.88.87:28075.

Map and rules

Which settings and rules does 111 run?

The name 111 carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has 111 loaded?

Size 3,000, seed 1413963070: the procedural map on 111, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does 111 wipe, and on what schedule?

111 wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 13 hours ago.

On 111, what happens on wipe day?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags, lists

Where does 111 appear among Rust Data lists and filters?

The Rust Data lists that 111 fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

How should you read the server tags on 111?

These tags are published by 111 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join 111?

In Rust, F1 opens the console: type client.connect 157.85.88.87:28075. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp1
Max players 1 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins 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.

Rust Data 41,782 players 11,662 servers online