The server's own banner, as it publishes it
Exhibit no. 709Acc. 2026.0709
JP RustPvE kokuu Server No kill No raid beeginner
Rust server · in the archive since 13 September 2026
Online 162.43.5.201:28015 checked 11m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
13 Sep Now 1 Oct18:13 · FW 5 Nov19:00 · FW 3 Dec19:00 · FW
a wipe on recordthe monthly force wipeexpectednow, 28 Oct 2026, 03:30 UTCAll times UTC.
The record of each wipe
-
Thu 1 Oct 202618:13 UTC FW26d ago
- Peak
- 91+2 in the queue
- Crowd
- –
- Lasted
- running
- Players before
- 20
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.
The rhythm
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence
Coming wipes
- 8d 15hThu 5 Nov, 19:00 UTCFW
- 36d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 91, 20 hours in, with 2 in the queue.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 3% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags, lists
What do the server tags on JP RustPvE kokuu Server No kill No raid beeginner mean?
You can see the tags JP RustPvE kokuu Server No kill No raid beeginner publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): The server runs game protocol 2635; matching it is required to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): No region code is set; ^m (Monthly): A monthly wipe applies here, as does the force wipe from Facepunch; ^v (Vanilla): Nothing is changed from Facepunch's release: no altered rates, no kits, no extra rules; ^p (PvE): The danger comes from the world, not other players. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.
Which Rust Server History lists and filters include JP RustPvE kokuu Server No kill No raid beeginner?
The Rust Server History lists that feature JP RustPvE kokuu Server No kill No raid beeginner are: Rust community servers, Rust PvE servers, on record and The vanilla Rust servers on record. These filters on the server list bring it up: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v and PvE ^p; Group limit: 5 or more; Wipe schedule: Monthly; Average players: 10+ on average.
The record
Does JP RustPvE kokuu Server No kill No raid beeginner run smoothly?
Across the last 48 hours it averaged 55 server fps; the low was 40. Buildings, deployables and everything else in the world came to as many as 162,687 entities. Up to 5,595 MB of memory was used. What players feel as lag comes from low fps and a climbing entity count.
Which version of Rust does JP RustPvE kokuu Server No kill No raid beeginner run?
Rust network protocol 2635 and build 168909 is the build JP RustPvE kokuu Server No kill No raid beeginner runs, on Linux. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is JP RustPvE kokuu Server No kill No raid beeginner online, and how reliable is it?
The live count shows JP RustPvE kokuu Server No kill No raid beeginner online right now. Going by its reported uptime, it restarted about 24 hours ago. 168 of 168 hours, or 100% of the time, over the last 7 full days. 13 September 2026 is when Rust Server History first saw it.
Where is JP RustPvE kokuu Server No kill No raid beeginner located?
Its name points to Asia, though JP RustPvE kokuu Server No kill No raid beeginner publishes no region tag. The location on Rust Server History is what a server says, not a lookup of where the machine stands. You can reach it at 162.43.5.201:28015.
Wipe log
What does wipe day look like on JP RustPvE kokuu Server No kill No raid beeginner?
An average peak of 91 players was drawn by its recent wipes. With 2 more waiting in the queue, the crowd peaked 20 hours after the latest wipe.
What is the wipe schedule on JP RustPvE kokuu Server No kill No raid beeginner?
Once a month JP RustPvE kokuu Server No kill No raid beeginner wipes, with the force wipe. On Thursday 5 November at 19:00 UTC comes the force wipe, its next wipe, when every Rust server wipes. The world it runs now dates from 26 days 9 hours ago. The tags list a monthly wipe schedule.
Player record
How does JP RustPvE kokuu Server No kill No raid beeginner rank against other Rust servers?
The last seven days of player hours place JP RustPvE kokuu Server No kill No raid beeginner at #709, among the top 3% of all ranked servers.
How busy is JP RustPvE kokuu Server No kill No raid beeginner?
Against 200 slots, JP RustPvE kokuu Server No kill No raid beeginner records 6 players right now. Stored history gives a seven-day average of 17 players and a peak of 57. An average of 36 players at 13:00 UTC made that the busiest hour of the last 48.
Rules, map
What are the rules and settings on JP RustPvE kokuu Server No kill No raid beeginner?
No gather rate is stated in the name of JP RustPvE kokuu Server No kill No raid beeginner. The limit of 8 players per group is the game's default. Under game mode, the entry reads pve, no combat against other players. The server browser lists it under Community, as a community server. The server applies the label vanilla: nothing is changed from Facepunch's release: no altered rates, no kits, no extra rules. The anti-cheat VAC from Valve is active.
Which map does JP RustPvE kokuu Server No kill No raid beeginner run?
A procedural map of size 4,250 with seed 682016 is what JP RustPvE kokuu Server No kill No raid beeginner runs, generated by the game. You can look at the map on RustMaps from this page, since one size and seed always give one map.
How to join
How do I join JP RustPvE kokuu Server No kill No raid beeginner?
Enter client.connect 162.43.5.201:28015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you. https://discord.com/invite/MkAJz45E7 is its website.
The label explained
Server tags
What each tag this server publishes means.
Published as mp200,ptrak,$r?,v2635,^m,^v,^p,gmrust,cs168909,ts8
Game
gmrust
mp200
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^m
Difficulty
^v
Gameplay
^p
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.