Online 151.80.25.50:28012 checked 9m ago
cinematic
Connect
srv = rust.server("151.80.25.50:28022")
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 bestTop 69% 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 13h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 13h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 13h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:58 UTC FW27d 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
4500 · seed 8540
- map
- Procedural Map
- size
- 4500
- seed
- 8540
Server
srv.info()- address
- 151.80.25.50:28012
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:58 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 537 on average | 162/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 152/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 281 on average | 14/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 18/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 248 on average | 66/200 |
Quick answers
From the figures on this page.
Population
How does cinematic compare in the rankings?
Over the last seven days cinematic sits at #15,341 on player hours, in the top 69% of ranked servers.
How many players does cinematic hold at once?
cinematic reports 0 players at this refresh, with 5 slots configured. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on cinematic?
The 48-hour average is 1 server fps, with a low of 1. Entity numbers reached 111,316, and that includes buildings, deployables and the rest. Memory peaked at 3,185 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is cinematic on?
Rust network protocol 2635 and build 168909 on Linux is what cinematic runs. Steam updates your game for you, but the protocol must match to join.
Is cinematic up, and what does its uptime show?
Online is the state at the latest refresh for cinematic. The uptime it reports puts the last restart about 2 days 22 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does cinematic sit?
For cinematic, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 151.80.25.50:28012.
Map and rules
Which rules apply on cinematic, and what settings?
You will not find a gather rate in the string cinematic. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has cinematic selected?
cinematic runs a procedural map of size 4,500 with seed 8540, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does cinematic wipe, and on what schedule?
Once a month cinematic wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 27 days 12 hours ago.
On cinematic, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold cinematic, and which filters?
The Rust Data lists that cinematic fits are: 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 cinematic hold?
These tags are published by cinematic and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; 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): Region code: not set. 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 cinematic?
In Rust, F1 opens the console: type client.connect 151.80.25.50:28012. Launch Rust on this page does the same by opening the game through Steam and connecting.