Rust Data

rustdata.spaceservers157.85.91.111:28016.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.91.111:28015 checked 25m ago

FIND GUZMAN

moddedoxide

Connect

srv = rust.server("157.85.91.111:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 1 # peak 4
rank #3,900 # top 18%
last wipe 11d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5217:0002:0011:0021:0006:0015:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040017:0002:0011:0021:0006:0015:00

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 17 Sep. 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
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 18% 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 gap14.6 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 1.5

The first 48 hours of its last wipes

Sat 17 OctThu 1 OctThu 17 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 46 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 17 Oct, 04:13 UTC11d ago 4 NaN running 3
1 Thu 1 Oct, 22:18 UTC FW26d ago 1 halved by day 2 15.2 days 0
2 Thu 17 Sep, 21:35 UTC40d ago 5 halved by day 1 14 days 0

# 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

2500 · seed 4815162
Map of FIND GUZMAN
map
Procedural Map
size
2500
seed
4815162
Open on RustMaps

Server

srv.info()
address
157.85.91.111:28015
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
17 Oct 2026, 04:13 UTC
hostname
–
first seen
13 Sep 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 · 156 on average211/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average177/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 89 on average136/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average19/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average52/1000

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does FIND GUZMAN rank?

Player hours over seven days put FIND GUZMAN at #3,900, in the top 18% of the ranked set.

How many players does FIND GUZMAN hold at once?

The sample now reads 0 players for FIND GUZMAN, out of 40 slots. Over the last seven days it averaged 1 players and peaked at 4. Averaged by hour over 48 hours, 05:00 UTC is the busiest, at 1 players.

Server facts

How smoothly does FIND GUZMAN run?

Averaged over 48 hours: 215 server fps, never under 168. The entity count peaked at 30,305, covering buildings, deployables and the rest of the world. The memory field tops out at 3,577 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on FIND GUZMAN?

Version Rust network protocol 2635 and build 168909 on Linux is reported by FIND GUZMAN. The protocol has to match before you can join, and Steam does the updating.

How reliable is FIND GUZMAN, and is it online now?

Online is the state at the latest refresh for FIND GUZMAN. Count back 3 days 8 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 13 September 2026.

Where does FIND GUZMAN sit?

No region is published by FIND GUZMAN. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 157.85.91.111:28015 is its address.

Map and rules

Which rules apply on FIND GUZMAN, and what settings?

No gather rate appears in the name: FIND GUZMAN. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on FIND GUZMAN?

FIND GUZMAN runs a procedural map of size 2,500 with seed 4815162, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does FIND GUZMAN wipe, and on what schedule?

FIND GUZMAN wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 12 hours ago.

On FIND GUZMAN, what happens on wipe day?

The average peak over recent wipes is 3 players. 46 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 1.5 in the other cases.

Tags, lists

Which Rust Data filters and lists contain FIND GUZMAN?

The Rust Data lists that FIND GUZMAN fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on FIND GUZMAN hold?

The game's server browser reads these tags from FIND GUZMAN: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to FIND GUZMAN?

Enter client.connect 157.85.91.111:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 87,533 players 11,823 servers online