Online 203.16.163.36:20797 checked 12m ago
RUBIN.EXE
Connect
srv = rust.server("203.16.163.36:20798")
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 25% 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 3, 18 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:05 UTC FW27d ago | 3 | NaN | running | 0 |
| 1 | Tue 15 Sep, 10:01 UTC43d ago | 1 | halved by day 5 | 16.5 days | 0 |
| 2 | Mon 14 Sep, 01:21 UTC45d ago | 1 | NaN | 1.4 days | 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
2500 · seed 50000
- map
- Procedural Map
- size
- 2500
- seed
- 50000
Server
srv.info()- address
- 203.16.163.36:20797
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:05 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 · 150 on average | 105/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 136/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 47/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Player counts
What position does RUBIN.EXE take in the server rankings?
Rank #5,568 on seven-day player hours for RUBIN.EXE, within the top 25% of all ranked servers.
How full does RUBIN.EXE run?
The sample now reads 0 players for RUBIN.EXE, out of 30 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 20:00 UTC is the busiest, at 1 players.
Server facts
What does performance look like on RUBIN.EXE?
The 48-hour average is 226 server fps, with a low of 195. Buildings, deployables and all else in the world took the count as high as 30,383 entities. The memory field tops out at 3,712 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on RUBIN.EXE?
Version Rust network protocol 2635 and build 168909 on Linux is reported by RUBIN.EXE. The protocol has to match before you can join, and Steam does the updating.
Is RUBIN.EXE up, and what does its uptime show?
Online is the state at the latest refresh for RUBIN.EXE. The uptime it reports puts the last restart about 2 days 20 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.
Which location does RUBIN.EXE run from?
For RUBIN.EXE, 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 203.16.163.36:20797.
Settings and map
What rules and settings are recorded for RUBIN.EXE?
No gather rate appears in the name: RUBIN.EXE. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. Anti-cheat status: VAC off.
Which map has RUBIN.EXE selected?
The game generates the map on RUBIN.EXE: procedural, size 2,500, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does RUBIN.EXE wipe?
No next wipe can be predicted for RUBIN.EXE, which wipes at irregular times. 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 27 days 10 hours ago.
On RUBIN.EXE, what happens on wipe day?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 18 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 5 in the other cases.
Lists and tags
Which Rust Data filters and lists contain RUBIN.EXE?
On Rust Data, RUBIN.EXE appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on RUBIN.EXE hold?
These tags are published by RUBIN.EXE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): Slot count: 30; 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): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to RUBIN.EXE?
In Rust, F1 opens the console: type client.connect 203.16.163.36:20797. Launch Rust on this page does the same by opening the game through Steam and connecting.