Online 65.21.78.173:28015 checked 10m ago
Ramboot
Connect
srv = rust.server("65.21.78.173: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 · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 8h | 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, 18:06 UTC FW26d 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
3700 · seed 445948691
- map
- Procedural Map
- size
- 3700
- seed
- 445948691
Server
srv.info()- address
- 65.21.78.173:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:06 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 · 540 on average | 530/575 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 358/400 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 314 on average | 36/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 313 on average | 44/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 273 on average | 152/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 79/100 |
Quick answers
From the figures on this page.
Population
What position does Ramboot take in the server rankings?
Over the last seven days Ramboot sits at #15,399 on player hours, in the top 69% of ranked servers.
What population does Ramboot carry?
The sample now reads 0 players for Ramboot, out of 50 slots. Over the last seven days it averaged 0 players.
About the server
How well does Ramboot perform?
The 48-hour average is 136 server fps, with a low of 113. The entity count peaked at 77,598, covering buildings, deployables and the rest of the world. Memory peaked at 3,192 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Ramboot run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by Ramboot. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Ramboot, and is it up?
Ramboot reports itself online at the current refresh. Count back 5 days 14 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is Ramboot hosted?
There is no region published for Ramboot. 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 65.21.78.173:28015.
Rules, settings, map
What rules and settings are recorded for Ramboot?
No gather rate appears in the name: Ramboot. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.
What is the map on Ramboot?
The game generates the map on Ramboot: procedural, size 3,700, seed 445948691. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Ramboot wipe, and how often?
The only wipe Ramboot takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 26 days 16 hours ago.
On Ramboot, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does Ramboot appear among Rust Data lists and filters?
The Rust Data lists that Ramboot fits are: Rust community servers, unfiltered. It appears under these filters 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 Ramboot hold?
These tags are published by Ramboot and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 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 Ramboot?
Enter client.connect 65.21.78.173:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
