Offline 31.134.188.77:28015 checked 2d ago
10.145.64.33
Connect
srv = rust.server("31.134.188.77: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. 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 32% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 17 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 22:20 UTC7d ago | 1 | NaN | running | 0 |
| 1 | Sat 17 Oct, 23:51 UTC12d ago | 1 | held half | 4.9 days | 0 |
| 2 | Tue 13 Oct, 12:23 UTC16d ago | 0 | NaN | 4.5 days | 0 |
| 3 | Mon 5 Oct, 18:43 UTC24d ago | 0 | NaN | 7.7 days | 1 |
| 4 | Sat 26 Sep, 21:23 UTC33d ago | 1 | NaN | 8.9 days | 1 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 31.134.188.77:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 22:20 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 · 495 on average | 84/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 397/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 21/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 476/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 362/425 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does 10.145.64.33 rank?
Player hours over seven days put 10.145.64.33 at #7,173, in the top 32% of the ranked set.
How full does 10.145.64.33 run?
The current row shows 10.145.64.33 offline; the last response was 2 days 22 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What Rust version does 10.145.64.33 run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by 10.145.64.33. Steam updates your game for you, but the protocol must match to join.
Is 10.145.64.33 up, and what does its uptime show?
The latest sample has 10.145.64.33 offline, with a last sighting 2 days 22 hours ago. Uptime of 12% across the last 7 full days: 20 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is 10.145.64.33 hosted?
There is no region published for 10.145.64.33. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 31.134.188.77:28015.
Rules, settings, map
Which rules apply on 10.145.64.33, and what settings?
The name 10.145.64.33 carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.
Which map has 10.145.64.33 loaded?
A procedural map runs on 10.145.64.33, generated by the game.
Wipe schedule
On what schedule does 10.145.64.33 wipe?
Irregular wipe times on 10.145.64.33 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. The world it runs now was generated 7 days 2 hours ago.
On 10.145.64.33, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 17 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags, lists
Which Rust Data filters and lists contain 10.145.64.33?
These Rust Data lists include 10.145.64.33: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on 10.145.64.33?
These tags are published by 10.145.64.33 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $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
What is the way into 10.145.64.33?
In Rust, F1 opens the console: type client.connect 31.134.188.77:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.