Online 121.1.248.130:37600 checked 7m ago
RiSu-Test Server
Connect
srv = rust.server("121.1.248.130:38624")
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 49% 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 7d 7h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 7h | 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 1, 3 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 08:55 UTC25d ago | 1 | NaN | running | 0 |
| 1 | Sun 27 Sep, 23:55 UTC31d ago | 1 | halved by day 3 | 6.4 days | 0 |
| 2 | Mon 14 Sep, 12:21 UTC44d ago | 1 | halved by day 8 | 13.5 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
4000 · seed 1337
- map
- Custom Map
- size
- 4000
- seed
- 1337
Server
srv.info()- address
- 121.1.248.130:37600
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 4 Oct 2026, 08:55 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 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 12/300 |
| 1 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 50 on average | 22/200 |
| 2 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 38 on average | 11/200 |
| 3 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 40/100 |
| 4 | Zombie Land PVE Monthly | Raids | Skills | Custom Maps | NA · groups of 14+ · monthly · 34 on average | 10/100 |
| 5 | Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | Jet | NA · no group limit · 1x · monthly · 34 on average | 56/100 |
Quick answers
From the figures on this page.
Population data
How does RiSu-Test Server compare in the rankings?
Over the last seven days RiSu-Test Server sits at #10,915 on player hours, in the top 49% of ranked servers.
What population does RiSu-Test Server carry?
The sample now reads 1 players for RiSu-Test Server, out of 2 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 12:00 UTC is the busiest, at 1 players.
About the server
How well does RiSu-Test Server perform?
The 48-hour average is 48 server fps, with a low of 44. Entity numbers reached 103,847, and that includes buildings, deployables and the rest. Memory peaked at 2,844 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on RiSu-Test Server?
Rust network protocol 2635 and build 168909 on Linux is what RiSu-Test Server runs. The protocol has to match before you can join, and Steam does the updating.
Is RiSu-Test Server up, and what does its uptime show?
RiSu-Test Server reports itself online at the current refresh. A restart about 1 hours ago is what its reported uptime implies. Uptime of 12% across the last 7 full days: 21 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does RiSu-Test Server run from?
For RiSu-Test Server, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 121.1.248.130:37600 is its address.
Rules, settings, map
What rules and settings are recorded for RiSu-Test Server?
The name RiSu-Test Server carries no gather rate. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has RiSu-Test Server selected?
Size 4,000, seed 1337: the procedural map on RiSu-Test Server, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe data
When does RiSu-Test Server wipe, and how often?
A single wipe each month, the force wipe, is all RiSu-Test Server does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 25 days 3 hours ago, and that is the one in play. The tags list wipes as monthly.
What is wipe day on RiSu-Test Server like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 3 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.5 in the other cases.
Tags, lists
Where does RiSu-Test Server appear among Rust Data lists and filters?
On Rust Data, RiSu-Test Server appears in these lists: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on RiSu-Test Server?
These tags are published by RiSu-Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 RiSu-Test Server?
The manual route: launch Rust, F1, then client.connect 121.1.248.130:37600. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.