Online 144.48.106.188:28015 checked 7m ago
Clam Observatory
Connect
srv = rust.server("144.48.106.188:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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 1871388706
- map
- Procedural Map
- size
- 3500
- seed
- 1871388706
Server
srv.info()- address
- 144.48.106.188:28015
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 03: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)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 183/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 343/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 246/700 |
Quick answers
From the figures on this page.
Population data
What position does Clam Observatory take in the server rankings?
Player hours over seven days put Clam Observatory at #15,344, in the top 69% of the ranked set.
What population does Clam Observatory carry?
Current row: 0 players on Clam Observatory, against 30 slots. Over the last seven days it averaged 0 players.
Server data
How smoothly does Clam Observatory run?
The 48-hour average is 93 server fps, with a low of 45. Buildings, deployables and all else in the world took the count as high as 63,666 entities. Memory peaked at 3,078 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Clam Observatory on?
The build is Rust network protocol 2633 and build 162929 on Windows, run by Clam Observatory. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Clam Observatory, and is it online now?
The current sample puts Clam Observatory online. The uptime it reports puts the last restart about 4 days 1 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Clam Observatory run from?
For Clam Observatory, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 144.48.106.188:28015 is its address.
Settings and map
Which settings and rules does Clam Observatory run?
The name Clam Observatory carries no gather rate. 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. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Clam Observatory selected?
Clam Observatory runs a procedural map of size 3,500 with seed 1871388706, 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
When does Clam Observatory wipe, and how often?
Too few wipes are on record for Clam Observatory to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 55 days 12 hours ago, and that is the one in play.
Tags and filters
Which lists on Rust Data hold Clam Observatory, and which filters?
The Rust Data lists that Clam Observatory 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.
Which meanings do the tags on Clam Observatory hold?
Read by the game's server browser, the tags Clam Observatory publishes are: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.
How to join
What is the way to join Clam Observatory?
In Rust, F1 opens the console: type client.connect 144.48.106.188:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.