Online 122.51.62.110:28036 checked 10m ago
2203
Connect
srv = rust.server("122.51.62.110:28036")
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 18 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 · 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 28 Sep, 14:38 UTC30d ago | 1 | 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
3600 · seed 114514- map
- Procedural Map
- size
- 3600
- seed
- 114514
Server
srv.info()- address
- 122.51.62.110:28036
- region
- –
- max players
- 32
- group limit
- not published
- wipe schedule
- –
- last wipe
- 28 Sep 2026, 16:17 UTC
- hostname
- –
- first seen
- 18 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 · 149 on average | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 69/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/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.
Population data
How does 2203 compare in the rankings?
Over the last seven days 2203 sits at #15,323 on player hours, in the top 69% of ranked servers.
How full does 2203 run?
2203 reports 0 players at this refresh, with 32 slots configured. Over the last seven days it averaged 0 players.
Server data
How smoothly does 2203 run?
The 48-hour average is 10 server fps, with a low of 10. Entity numbers reached 41,168, and that includes buildings, deployables and the rest. A high of 1,130 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is 2203 on?
The build is Rust network protocol 2203 on Windows, run by 2203. Steam updates your game for you, but the protocol must match to join.
How reliable is 2203, and is it up?
Online is the state at the latest refresh for 2203. A restart about 5 days 15 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 18 September 2026.
In which location is 2203 hosted?
No region is published by 2203. Rust Data does not look up where the machine stands; it shows where a server says it is. 122.51.62.110:28036 is its address.
Settings and map
Which settings and rules does 2203 run?
No gather rate appears in the name: 2203. The field for group size is empty. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Anti-cheat status: VAC off.
Which map has 2203 selected?
The game generates the map on 2203: procedural, size 3,600, seed 114514. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
On what schedule does 2203 wipe?
The record for 2203 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. This world was created 30 days 19 hours ago.
What is wipe day on 2203 like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which Rust Data filters and lists contain 2203?
The Rust Data lists that 2203 fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded.
Which meanings do the tags on 2203 hold?
The game's server browser reads these tags from 2203: gmrust (Game mode): Rust survival in its standard form; mp32 (Max players): 32 slots in total; v2203 (Protocol): The server speaks protocol 2203, so match your game version; oxide (Oxide): Plugin framework: Oxide (uMod); modded (Modded): Plugins or settings alter the game, so it sits under Modded; h3d581950 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin; stok (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into 2203?
The manual route: launch Rust, F1, then client.connect 122.51.62.110:28036. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.