Rust Data LabData lab · live
Live readings Servers11,891 Players103,453 Populated4,007 Fresh wipes · 3h409 Sampled every 5 min

Element card · group Modded · atomic number 4,782, its rank

测试123456789

Online 118.178.196.247:28015 checked 15m ago

moddedoxide
Join the experiment
Atomic mass · players now 1/ 1 100% full Near capacity
7-day average1peak 1
Rank · atomic number#4,782top 21%
Last wipe5h agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeakWipe
00.250.50.75120:0004:0013:0022:0007:0017:00Wiped Thu 29 Oct, 13:34 UTCWIPE

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
Server fpsWipe
010020030040020:0004:0013:0022:0007:0017:00Wiped Thu 29 Oct, 13:34 UTCWIPE

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

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

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

Reaction kinetics

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 27 OctMon 26 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 13:34 UTC5h ago – – running 1
Tue 27 Oct, 03:08 UTC2d ago 1+1 queue held half 2.4 days 0
Mon 26 Oct, 03:43 UTC3d ago 1 – 1 days 1

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
  1. 1 Qs QS『芬达』100000倍/… 33
    QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 EA · groups of 20+ · weekly · 25 on average 33/ 100
  2. 2 倍档 【蛋壳】10倍|10.23档… 33
    【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 EA · groups of 8+ · weekly · 21 on average 33/ 200
  3. 3 Jp [JP]初心者PVPサーバー… 1
    [JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 15 on average 1/ 100
  4. 4 倍p [守护]100倍PVE/迷雾… 18
    [守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新 EA · no group limit · 12 on average 18/ 100
  5. 5 倍日 [霸道]10000000倍-… 18
    [霸道]10000000倍-10.29日-萌新首选-稳定长久 EA · no group limit · 12 on average 18/ 100
  6. 6 搞就 #10-[搞就完了]10倍/… 20
    #10-[搞就完了]10倍/10.29新档/无权/萌新首选 EA · no group limit · 11 on average 20/ 100

Quick answers

from the figures on this page

Server setup

What map is in play on 测试123456789?

A procedural map of size 3,500 with seed 1573025114 runs on 测试123456789, generated by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

How is 测试123456789 configured, and what rules apply?

The name of 测试123456789 carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. You can fight other players and raid them. Plugins or settings change the game, so the browser lists it under Modded. The plugin count is Oxide. VAC is off, Valve's anti-cheat.

About the server

Which location is 测试123456789 based in?

Going by its name rather than a tag, 测试123456789 points to Asia. Rust Data Lab shows a server's stated location, not a verified position of the machine. Connect at 118.178.196.247:28015.

What Rust version does 测试123456789 currently run?

Rust network protocol 2635 and build 168909 on Windows is what 测试123456789 uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does 测试123456789 stay online?

Right now, 测试123456789 is reachable. About 57 minutes ago is when it last restarted, based on its uptime. It was online for 70 of 72 hours in the last 3 full days, which is 97% uptime. On 25 October 2026, Rust Data Lab saw it for the first time.

How well does 测试123456789 perform?

Server fps averaged 158 over the last 48 hours, with 108 as the lowest. The maximum entity count was 75,699, covering buildings, deployables and all else in the world. Memory use peaked at 3,251 MB. What players experience as lag comes from low fps and a rising entity count.

Wipe days

What is the wiping pattern on 测试123456789?

With no fixed rhythm, 测试123456789 wipes at irregular times, so the next wipe cannot be predicted. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 5 hours ago.

How does 测试123456789 look on the day of a wipe?

Averaged across its recent wipes, the busiest point drew 1 players. 1 hours after the latest wipe the crowd peaked, and a further 1 waited in the queue. Half that peak was held until the next wipe in 100% of recent wipes.

Lists and tags

What should you understand from the tags 测试123456789 carries?

The game's server browser reads the tags 测试123456789 publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Player slots: 1; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): It runs build 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): Plugins or settings alter the game, so it lists under Modded. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does 测试123456789 appear in?

These themed Rust Data Lab lists carry 测试123456789: Modded Rust servers, measured. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Player counts

Against other Rust servers, where does 测试123456789 place?

测试123456789 sits at #4,782 for seven-day player hours, placing it in the top 21% of ranked servers.

What does the current player count on 测试123456789 tell you?

测试123456789 currently shows 1 players across 1 slots. A seven-day sample gives 1 players on average and 1 at the top. Peak time in the past 48 hours: 03:00 UTC, when the average was 1 players.

How to join

What is the way to join 测试123456789?

Open the console with F1 in Rust and type client.connect 118.178.196.247:28015. The Launch Rust button on this page does the same job through Steam. Expect a queue: it is full right now.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp1
Max players Player slots: 1.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build It runs build 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.