nomarust Long | JP | Vanilla | Monthly
Online EA 160.16.60.191:31015 checked 10m ago
Measurements
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 12% of all ranked servers, top 45% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 47, 47 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 25 Sep, 12:09 UTC34d ago | 47 | – | running | 3 |
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.
Quick answers
Population
How does nomarust Long | JP | Vanilla | Monthly rank against other Rust servers?
On player hours over the last seven days nomarust Long | JP | Vanilla | Monthly is #2,568, #242 in Asia, placing it in the top 12% of ranked servers.
How busy is nomarust Long | JP | Vanilla | Monthly?
Of its 200 slots, nomarust Long | JP | Vanilla | Monthly is using 2 right now. Seven days of counting give an average of 1 players and a peak of 8. In the last 48 hours the peak hour came at 11:00 UTC, averaging 6 players.
Lists and tags
What do the server tags on nomarust Long | JP | Vanilla | Monthly mean?
The game's server browser reads the tags nomarust Long | JP | Vanilla | Monthly publishes: gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^m (Monthly): This server wipes once a month, at the same time as Facepunch's force wipe; ^v (Vanilla): No kits, no rate changes, no rules added: the game as Facepunch ships it; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; EA (East Asia): In the server browser it appears under East Asia. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include nomarust Long | JP | Vanilla | Monthly?
On Rust Population, nomarust Long | JP | Vanilla | Monthly is filed under these lists: Community servers, field-listed and Vanilla Rust servers, counted. Look for it under these filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Wipe schedule
What does wipe day look like on nomarust Long | JP | Vanilla | Monthly?
Averaged over recent wipes, 47 players were counted at the busiest point. The crowd on the latest wipe peaked 47 hours in.
What is the wipe schedule on nomarust Long | JP | Vanilla | Monthly?
nomarust Long | JP | Vanilla | Monthly wipes with the force wipe and at no other time, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Counted from 34 days 5 hours ago, that is how long the current world has stood. Its tags give a wipe schedule of one wipe a month.
Map and rules
Which map does nomarust Long | JP | Vanilla | Monthly run?
A procedural map of size 5,000 from seed 1790337682, generated by the game, is in use on nomarust Long | JP | Vanilla | Monthly. The map follows from its size and seed, and RustMaps shows it from this page.
What are the rules and settings on nomarust Long | JP | Vanilla | Monthly?
Nothing in nomarust Long | JP | Vanilla | Monthly's name says how gather works. The group limit is 8 players, which is the default. You get survival here, raid, build and gather: the standard game. Combat between players, raids included, is permitted. The server browser lists it under Community, as a community server. The plugins it runs are Oxide. The server describes itself as vanilla: no kits, no rate changes, no rules added: the game as Facepunch ships it. VAC, Valve's anti-cheat, runs here.
About the server
Which version of Rust does nomarust Long | JP | Vanilla | Monthly run?
The setup is Rust network protocol 2635 and build 168909 on Linux for nomarust Long | JP | Vanilla | Monthly. Steam updates your game automatically, but you need the same protocol to join.
Does nomarust Long | JP | Vanilla | Monthly run smoothly?
In the last 48 hours, it averaged 86 server fps, with a low of 61. The entity count reached 145,471: buildings, deployables and all other objects. The highest memory usage was 4,114 MB. What players experience as lag comes from low fps and a rising entity count.
Is nomarust Long | JP | Vanilla | Monthly online, and how reliable is it?
nomarust Long | JP | Vanilla | Monthly is up and running at the moment. Judging by the uptime it reports, the last restart was about 3 hours ago. Over the last 7 full days, 167 of 168 hours were online, or 99%. It was first seen by Rust Population on 13 September 2026.
Where is nomarust Long | JP | Vanilla | Monthly located?
With its EA tag, nomarust Long | JP | Vanilla | Monthly places itself in Asia. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. 160.16.60.191:31015 is where it lives.
Getting in
How do I join nomarust Long | JP | Vanilla | Monthly?
Either enter client.connect 160.16.60.191:31015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected. For more, visit its website: https://discord.com/invite/nAyqFErqV4.