RusticainJP

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 9m ago · 220.158.22.173:28015

Abstract

We describe the public Rust server RusticainJP, reached at 220.158.22.173:28015. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 1¹. It ranks #11,213 of all servers, the top 50%. It last wiped 4d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/50	0% full
In the queue	0	no queue
Seven-day mean	0	peak 1
Rank²	#11,213	top 50%
Last wipe	4d ago	no schedule published
Next wipe³	–	too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

Figure 2: Server performance. 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.

4Rank

The server stands in the top 50% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	35.7 days	between real wipes
Wipe-day peak	1	players, last three wipes
Crowd held	0%	else halves by day 3

Sat 24 OctFri 18 Sep

Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Sat 24 Oct, 07:074d ago	1	–	running	0
Fri 18 Sep, 13:2839d ago	1	halved by day 3	35.7 d	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of RusticainJP — Figure 5: The map: Procedural Map, size 4000, seed 2147483647. Open on RustMaps.

Table 4: The server's published settings.

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
Map	Procedural Map
Size	4000
Seed	2147483647

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 155 on average	157/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 24.10EU · groups of 8+ · weekly · 128 on average	130/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average	184/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average	111/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 87 on average	8/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	45/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does RusticainJP perform well?

The server fps averaged 90 over the last 48 hours, never dropping below 52. The highest number of entities it carried was 99,028, comprising buildings, deployables and all other objects. The peak memory usage was 2,056 MB. Players experience lag when fps is low and the entity count is rising.

A.2In which location is RusticainJP based?

There is no region published for RusticainJP. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 220.158.22.173:28015 is its address.

A.3How reliable is RusticainJP, and is it currently online?

RusticainJP is currently online. The uptime it reports indicates a restart about 1 hours ago. Its uptime over the last full days (7 days) was 34%, with 57 of 168 hours online. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on RusticainJP?

Rust network protocol 2635 and build 168909 is the version that RusticainJP runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5On what cycle does RusticainJP wipe?

Too few wipes by RusticainJP have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 4 days 2 hours have passed since the current world was generated.

A.6What happens on RusticainJP when wipe day arrives?

The average busiest point of recent wipes was 1 players. The crowd reached its maximum 0 hours after the latest wipe. Half the peak was sustained until the next wipe in 0% of recent wipes. In the other cases, the population fell below half by day 3.

Player count

A.7What position does RusticainJP occupy in the ranking of Rust servers?

Ranked by player hours across seven days, RusticainJP holds #11,213, in the top 50% of all ranked servers.

A.8At what level does RusticainJP operate in terms of players?

On RusticainJP, 0 of the 50 slots are occupied at present. The peak over seven days is 1, against an average of 0.

Tags and filters

A.9What is the meaning of the tags on RusticainJP?

Tags from RusticainJP, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): The slot count is 50; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can RusticainJP be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that RusticainJP fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Settings and map

A.11What are the settings and rules that govern RusticainJP?

No gather rate appears in the name of RusticainJP. The group cap is 8 players, which is the default in the game. survival is the game mode here; gather, build and raid: the standard game. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.

A.12On which map does RusticainJP take place?

The game generates RusticainJP's procedural map at size 4,000, from seed 2147483647. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.13How do you connect to RusticainJP?

Press F1 inside Rust to open the console and enter client.connect 220.158.22.173:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp50`	Max players. The slot count is 50.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2635`	Protocol. The game protocol is 2635; your client must match it to join.
`cs168909`	Build. Build 168909 is the one running.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. The region code is unset.
Mods and access
`^o`	Oxide. Plugins are handled by Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.