RUST METRICSFlight deck · live data
Data live Servers11,632 Players42,162 Populated3,029 Fresh wipes 3 h90 Scan5 min
‹ All servers1.33.10.223:28016
Offline Full Queue Fresh wipe Wipe due No query

[JPN]omis3750

Offline 1.33.10.223:28016 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,717top 67%
Last wipe27d agono schedule published
Next wipe7d 10hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep1 Oct5 Oct10 Oct14 Oct19 Oct

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 10hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 10hFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 20:46 UTC FW27d ago 1 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on [JPN]omis3750 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 3 hours after the wipe, the crowd peaked on the latest wipe.

How often does [JPN]omis3750 wipe, and when?

Once a month [JPN]omis3750 wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 27 days 11 hours ago the current world was made.

Tag meanings

Which tags does [JPN]omis3750 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Build 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from [JPN]omis3750. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [JPN]omis3750 appear in Rust Metrics lists and filters?

On Rust Metrics, [JPN]omis3750 sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does [JPN]omis3750 hold among Rust servers?

Ranking for [JPN]omis3750: #14,717 on seven-day player hours, top 67% of all ranked servers.

What is the population on [JPN]omis3750?

Reading for [JPN]omis3750: offline at this moment; last seen 16 days 10 hours ago.

Server details

What location is [JPN]omis3750 hosted in?

Reading: location. [JPN]omis3750 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 1.33.10.223:28016.

What Rust version is [JPN]omis3750 on?

Rust network protocol 2634 and build 167584 on Windows is the build [JPN]omis3750 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is [JPN]omis3750, and is it online now?

Reading: offline. [JPN]omis3750 last answered 16 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 26 September 2026.

Settings and map

How is [JPN]omis3750 configured, and what rules are in force?

Reading the name gives no gather rate for [JPN]omis3750. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [JPN]omis3750?

Check: map. Procedural, generated by the game, on [JPN]omis3750.

Join

How do you connect to [JPN]omis3750?

Check: join. Open Rust, press F1, then enter client.connect 1.33.10.223:28016. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Build 167584.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.