Rust Data

rustdata.spaceservers198.73.57.79:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 198.73.57.79:28015 checked 24d ago

CALI

Connect

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

Right now

srv.summary()
players now 0/150 # 0% full
7-day average 0 # peak –
rank #15,986 # top 71%
last wipe 24d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 4 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
15k10k15k20k20 Sep24 Sep28 Sep4 Oct8 Oct12 Oct

Top 71% 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 gap10.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Sun 4 OctMon 14 SepMon 14 Sep
01234+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 Sun 4 Oct, 22:12 UTC24d ago 1 NaN running 0
1 Mon 14 Sep, 13:49 UTC45d ago 4 halved by day 2 20.3 days 0
2 Mon 14 Sep, 06:39 UTC45d ago 4 NaN 0.3 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

3500 · seed 648252
Map of CALI
map
Procedural Map
size
3500
seed
648252
Open on RustMaps

Server

srv.info()
address
198.73.57.79:28015
region
–
max players
150
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 22:12 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
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 512 on average338/375
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average441/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average979/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average46/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average985/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 235 on average64/250

Quick answers

From the figures on this page.

Player counts

What position does CALI take in the server rankings?

Player hours over seven days put CALI at #15,986, in the top 71% of the ranked set.

What population does CALI carry?

Offline now for CALI, with the last sample 24 days 11 hours ago.

About the server

What Rust version does CALI run?

Version Rust network protocol 2634 and build 166652 on Windows is reported by CALI. Joining needs the same protocol on your game; Steam handles the update.

How reliable is CALI, and is it up?

The latest sample has CALI offline, with a last sighting 24 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is CALI hosted?

There is no region published for CALI. 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 198.73.57.79:28015.

Settings and map

Which settings and rules does CALI run?

The name CALI carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has CALI selected?

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

Wipes and dates

On what schedule does CALI wipe?

Irregular wipe times on CALI leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 24 days 20 hours ago, and that is the one in play.

What is wipe day on CALI like?

Across recent wipes the busiest point averaged 3 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. In the wipes where it did not hold, half was lost by day 2.

Tags and filters

Which Rust Data filters and lists contain CALI?

On Rust Data, CALI appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on CALI hold?

The game's server browser reads these tags from CALI: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): 150 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to CALI?

The manual route: launch Rust, F1, then client.connect 198.73.57.79: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 mp150,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp150
Max players 150 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build The server runs build 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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 103,803 players 11,888 servers online