Rust Server Analytics 39,834 players11,696 servers
All servers
Drill-through Server detail

GTR BPdrop JP

Online EA 162.43.24.19:28015 checked 9m ago

Drill-through
FilterServeris GTR BPdrop JP
Attributes
monthly wipes moddedoxidepve
Last refreshed
Players now 0/ 50
7-day average 2 peak 12
Rank #1,946 top 9% · #186 in EA
Last wipe 26d ago monthly schedule
Next wipe 7d 16h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
02.557.51003:0012:0021:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020003:0012:0021:0005:0014:0000:00

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
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 9% of all ranked servers, top 33% in EA. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

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

usual gap0.9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak31players, last three wipes
crowd held0%else halves by day 5

Coming wipes

InWhen, UTCKind
7d 16hThu 5 Nov, 19:00 UTCFW force wipe
35d 16hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Fri 2 OctThu 1 OctWed 30 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 33, 8 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:15 UTC26d ago 33 – running 2
Thu 1 Oct, 10:38 UTC27d ago 33 – 0.8 days 1
Wed 30 Sep, 13:01 UTC28d ago 26 – 0.9 days 1
Mon 21 Sep, 10:30 UTC37d ago 27 halved by day 5 9.1 days 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 35 on average 30 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 21 on average 16 / 88
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服 EA · groups of 8+ · monthly · 12 on average 14 / 100
[JP]ちょっぴりHard-PvE RiSu Server EA · groups of 8+ · monthly · 11 on average 6 / 100
【青岩-PVE服】原倍/萌新/突袭据点 EA · groups of 8+ · monthly · 11 on average 10 / 200
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 EA · groups of 16+ · monthly · 10 on average 11 / 100

Quick answers

from the figures on this page

Wipe data

When does GTR BPdrop JP wipe?

With the force wipe, once a month, GTR BPdrop JP wipes. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. 26 days 15 hours ago the current world was made. Its tags state a wipe schedule of one month.

Wipe day on GTR BPdrop JP: what should you expect?

Across recent wipes the busiest point averaged 31 players. 8 hours after the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The fall below half arrived by day 5 when it didn't hold.

Server details

What is the hosting location of GTR BPdrop JP?

Its EA tag puts GTR BPdrop JP in Asia. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 162.43.24.19:28015 is its address.

Which Rust version is GTR BPdrop JP on?

Rust network protocol 2635 and build 168909 on Linux is the setup for GTR BPdrop JP. The protocol has to match before you can join; Steam updates it automatically.

How reliable is GTR BPdrop JP, and is it online now?

The current status of GTR BPdrop JP is online. Its reported uptime indicates a restart roughly 5 hours ago. Uptime over the last full days (7) was 99%, or 167 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.

What performance does GTR BPdrop JP show?

The 48-hour average was 82 server fps; the low was 36. Entity count reached 141,207, covering buildings, deployables and the rest of the world. At its highest, memory use was 4,456 MB. Lag, for players, means low fps alongside a growing entity count.

Tags

How should the tags on GTR BPdrop JP be read?

The game's server browser reads the tags GTR BPdrop JP publishes: gmrust (Game mode): Rust survival, standard ruleset; mp50 (Max players): Capacity of 50 slots; ts15 (Group limit): Team size is capped at 15; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^p (PvE): The threat comes from the world, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): Its browser listing sits in East Asia. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

On Rust Server Analytics, which lists and filters feature GTR BPdrop JP?

Among the Rust Server Analytics lists GTR BPdrop JP fits are: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Player numbers

Where does GTR BPdrop JP sit among Rust servers?

Ranked on seven-day player hours, GTR BPdrop JP is #1,946 overall and #186 in Asia, within the top 9% of ranked servers.

How many players does GTR BPdrop JP carry?

Of 50 slots, 0 are filled on GTR BPdrop JP at this refresh. Averaging 2 players across seven days, the server reached a peak of 12. Averaged over 48 hours, activity is highest at 12:00 UTC with 6 players.

Map and rules

What are the settings on GTR BPdrop JP, and its rules?

Gather rate is not mentioned in the name of GTR BPdrop JP. A maximum of 15 players per group applies. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. Anti-cheat status: VAC on.

What is the map for GTR BPdrop JP?

A procedural map of size 4,250 with seed 1927854824, generated by the game, runs on GTR BPdrop JP. The map is reproducible from its size and seed and can be seen on RustMaps from here.

Connection

What is the way onto GTR BPdrop JP?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 162.43.24.19:28015. Find it online at https://discord.com/invite/WdbgNC2Uf2.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts15,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp50
Max players Capacity of 50 slots.
ts15
Group limit Team size is capped at 15.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Build number 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Wipe schedule

^m
Monthly A monthly cycle, with Facepunch's force wipe as the reset.

Gameplay

^p
PvE The threat comes from the world, not other players.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it sits under Modded.

Region

EA
East Asia Its browser listing sits in East Asia.

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.