Online 220.158.22.173:28015 checked 10m ago
RusticainJP
Connect
srv = rust.server("220.158.22.173:29015")
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 50% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 07:07 UTC5d ago | 1 | NaN | running | 0 |
| 1 | Fri 18 Sep, 13:28 UTC40d ago | 1 | halved by day 3 | 35.7 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
4000 · seed 2147483647
- map
- Procedural Map
- size
- 4000
- seed
- 2147483647
Server
srv.info()- address
- 220.158.22.173:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 07:07 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 | 74/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 105/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 36/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population data
What position does RusticainJP take in the server rankings?
Over the last seven days RusticainJP sits at #11,160 on player hours, in the top 50% of ranked servers.
How full does RusticainJP run?
RusticainJP reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How smoothly does RusticainJP run?
Server fps over the last 48 hours averages 90; the floor is 52. Entity numbers reached 99,157, and that includes buildings, deployables and the rest. A high of 1,977 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is RusticainJP on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by RusticainJP. The protocol has to match before you can join, and Steam does the updating.
Is RusticainJP up, and what does its uptime show?
RusticainJP reports itself online at the current refresh. A restart about 7 hours ago is what its reported uptime implies. 57 of 168 hours up over the last 7 full days, or 34%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does RusticainJP sit?
For RusticainJP, 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 220.158.22.173:28015.
Settings and map
Which rules apply on RusticainJP, and what settings?
No gather rate appears in the name: RusticainJP. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has RusticainJP selected?
RusticainJP runs a procedural map of size 4,000 with seed 2147483647, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does RusticainJP wipe, and on what schedule?
Too few wipes are on record for RusticainJP to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 5 days ago.
What is wipe day on RusticainJP like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 3.
Tags and filters
Which Rust Data filters and lists contain RusticainJP?
These Rust Data lists include RusticainJP: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on RusticainJP hold?
These tags are published by RusticainJP and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into RusticainJP?
Enter client.connect 220.158.22.173:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.