Online 15.204.68.165:27083 checked 12m ago
photo
Connect
srv = rust.server("15.204.68.165:27084")
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 37% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 11:53 UTC27d ago | 2 | 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
3000 · seed 660491287
- map
- Procedural Map
- size
- 3000
- seed
- 660491287
Server
srv.info()- address
- 15.204.68.165:27083
- region
- –
- max players
- 16
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 11:53 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 · 151 on average | 19/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 9/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 29/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 49/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does photo rank?
Player hours over seven days put photo at #8,211, in the top 37% of the ranked set.
How full does photo run?
Current row: 0 players on photo, against 16 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 10:00 UTC is the busiest, at 1 players.
Server data
How well does photo perform?
Server fps over the last 48 hours averages 182; the floor is 125. Entity numbers reached 46,725, and that includes buildings, deployables and the rest. Memory peaked at 4,303 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is photo on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by photo. Steam updates your game for you, but the protocol must match to join.
How reliable is photo, and is it online now?
The current sample puts photo online. Count back 27 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 86 of 168, 51%. Rust Data logged it first on 13 September 2026.
Where does photo sit?
No region is published by photo. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 15.204.68.165:27083.
Map and rules
Which rules apply on photo, and what settings?
You will not find a gather rate in the string photo. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has photo loaded?
photo runs a procedural map of size 3,000 with seed 660491287, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does photo wipe?
The record for photo holds too few wipes to show a rhythm. 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 27 days 16 hours ago, and that is the one in play.
On photo, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain photo?
On Rust Data, photo appears in these lists: 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.
Which meanings do the tags on photo hold?
The game's server browser reads these tags from photo: gmrust (Game mode): Survival play, standard Rust; mp16 (Max players): Slot count: 16; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: 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.
Join steps
What is the way to join photo?
In Rust, F1 opens the console: type client.connect 15.204.68.165:27083. Launch Rust on this page does the same by opening the game through Steam and connecting.