Rust Data

rustdata.spaceservers163.44.119.168:28017.ipynb

Run all rust-data · live

‹ All servers

Online 163.44.119.168:28015 checked 8m ago

RustServer_4656

moddedoxide

Connect

srv = rust.server("163.44.119.168:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #8,106 # top 36%
last wipe 28d ago # no schedule published
next wipe 7d 0h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75119:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304019:0004:0013:0023:0008:0017: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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 0h. # The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

inatkind
07d 0hThu 5 Nov, 19:00 UTCFW force wipe
135d 0hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:19 UTC FW28d ago 0 NaN running 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

5000 · seed 564841
Map of RustServer_4656
map
Procedural Map
size
5000
seed
564841
Open on RustMaps

Server

srv.info()
address
163.44.119.168:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 18:19 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 · 151 on average120/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average199/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average80/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 89 on average223/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average348/350

Quick answers

From the figures on this page.

Population data

What position does RustServer_4656 take in the server rankings?

Player hours over seven days put RustServer_4656 at #8,106, in the top 36% of the ranked set.

How full does RustServer_4656 run?

The sample now reads 0 players for RustServer_4656, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 23:00 UTC, mean 0 players.

Server data

What does performance look like on RustServer_4656?

Server fps over the last 48 hours averages 30; the floor is 21. Buildings, deployables and all else in the world took the count as high as 140,906 entities. Memory peaked at 5,288 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on RustServer_4656?

The build is Rust network protocol 2635 and build 168909 on Linux, run by RustServer_4656. Steam updates your game for you, but the protocol must match to join.

How reliable is RustServer_4656, and is it up?

RustServer_4656 reports itself online at the current refresh. A restart about 5 days 19 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

Where does RustServer_4656 sit?

No region is published by RustServer_4656. 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 163.44.119.168:28015.

Rules, settings, map

Which rules apply on RustServer_4656, and what settings?

The name RustServer_4656 carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has RustServer_4656 selected?

RustServer_4656 runs a procedural map of size 5,000 with seed 564841, 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

On what schedule does RustServer_4656 wipe?

The only wipe RustServer_4656 takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 28 days ago, and that is the one in play.

What is wipe day on RustServer_4656 like?

The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Where does RustServer_4656 appear among Rust Data lists and filters?

The Rust Data lists that RustServer_4656 fits are: 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.

Which meanings do the tags on RustServer_4656 hold?

These tags are published by RustServer_4656 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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

What is the way into RustServer_4656?

The manual route: launch Rust, F1, then client.connect 163.44.119.168:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 104,128 players 11,899 servers online