Online 70.237.29.165:28015 checked 9m ago
RustDockerServer
Connect
srv = rust.server("70.237.29.165:28016")
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 · 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 09:14 UTC26d 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 1337
- map
- Procedural Map
- size
- 4500
- seed
- 1337
Server
srv.info()- address
- 70.237.29.165:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 09:14 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 · 560 on average | 187/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 118/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 19/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 288 on average | 12/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 19/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 26/225 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does RustDockerServer rank?
Rank #15,353 on seven-day player hours for RustDockerServer, within the top 69% of all ranked servers.
How full does RustDockerServer run?
The sample now reads 0 players for RustDockerServer, out of 1 slots. Over the last seven days it averaged 0 players.
Server facts
How smoothly does RustDockerServer run?
Averaged over 48 hours: 129 server fps, never under 95. Entity numbers reached 121,769, and that includes buildings, deployables and the rest. The memory field tops out at 3,506 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does RustDockerServer run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by RustDockerServer. Steam updates your game for you, but the protocol must match to join.
How reliable is RustDockerServer, and is it up?
Online is the state at the latest refresh for RustDockerServer. The uptime it reports puts the last restart about 14 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is RustDockerServer hosted?
No region is published by RustDockerServer. 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 70.237.29.165:28015.
Map and rules
Which rules apply on RustDockerServer, and what settings?
No gather rate appears in the name: RustDockerServer. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has RustDockerServer selected?
RustDockerServer runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does RustDockerServer wipe, and on what schedule?
The record for RustDockerServer holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 16 hours ago.
On RustDockerServer, what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain RustDockerServer?
On Rust Data, RustDockerServer appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on RustDockerServer hold?
Read by the game's server browser, the tags RustDockerServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is 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.
Join steps
What is the way to join RustDockerServer?
Enter client.connect 70.237.29.165:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.