Rust Data

rustdata.spaceservers157.85.91.144:21140.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.91.144:21139 checked 12m ago

CODYS SOLO SERVER

moddedoxide

Connect

srv = rust.server("157.85.91.144:21140")
print(srv.connect_command)

Right now

srv.summary()
players now 0/8 # 0% full
7-day average 0 # peak 2
rank #9,548 # top 43%
last wipe 11d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123414:0023:0008:0018:0003:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040014:0023:0008:0018:0003:0012: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 12 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.5k10k12 Oct15 Oct18 Oct22 Oct25 Oct28 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap5.1 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 4

The first 48 hours of its last wipes

Sat 17 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 17 Oct, 02:57 UTC11d ago 4 NaN running 0
1 Mon 12 Oct, 00:43 UTC16d ago 3 halved by day 4 5.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

2500 · seed 744831120
Map of CODYS SOLO SERVER
map
Procedural Map
size
2500
seed
744831120
Open on RustMaps

Server

srv.info()
address
157.85.91.144:21139
region
–
max players
8
group limit
8, the default
wipe schedule
–
last wipe
17 Oct 2026, 02:57 UTC
hostname
–
first seen
11 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 · 156 on average174/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average133/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average155/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average131/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average14/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average48/1000

Quick answers

From the figures on this page.

Population

What position does CODYS SOLO SERVER take in the server rankings?

Player hours over seven days put CODYS SOLO SERVER at #9,548, in the top 43% of the ranked set.

How many players does CODYS SOLO SERVER hold at once?

The sample now reads 0 players for CODYS SOLO SERVER, out of 8 slots. Over the last seven days it averaged 0 players and peaked at 2.

Server facts

How smoothly does CODYS SOLO SERVER run?

Server fps over the last 48 hours averages 224; the floor is 196. Entity numbers reached 30,544, and that includes buildings, deployables and the rest. A high of 3,891 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on CODYS SOLO SERVER?

Rust network protocol 2635 and build 167781 on Linux is what CODYS SOLO SERVER runs. Joining needs the same protocol on your game; Steam handles the update.

Is CODYS SOLO SERVER up, and what does its uptime show?

CODYS SOLO SERVER reports itself online at the current refresh. A restart about 5 days 6 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 11 October 2026.

Where does CODYS SOLO SERVER sit?

No region is published by CODYS SOLO SERVER. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 157.85.91.144:21139.

Map and rules

What rules and settings are recorded for CODYS SOLO SERVER?

You will not find a gather rate in the string CODYS SOLO SERVER. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has CODYS SOLO SERVER loaded?

The game generates the map on CODYS SOLO SERVER: procedural, size 2,500, seed 744831120. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does CODYS SOLO SERVER wipe, and how often?

A rhythm cannot be read from the wipes of CODYS SOLO SERVER on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 11 days 10 hours ago, and that is the one in play.

On CODYS SOLO SERVER, what happens on wipe day?

The average peak over recent wipes is 4 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 4.

Tags, lists

Which lists on Rust Data hold CODYS SOLO SERVER, and which filters?

On Rust Data, CODYS SOLO SERVER appears in these lists: Modded Rust servers. 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 2 weeks.

Which meanings do the tags on CODYS SOLO SERVER hold?

These tags are published by CODYS SOLO SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): Slot count: 8; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join CODYS SOLO SERVER?

Enter client.connect 157.85.91.144:21139 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 mp8,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp8
Max players Slot count: 8.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs167781
Build Build number: 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

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 75,412 players 11,748 servers online