Rust Data

rustdata.spaceservers118.178.196.247:27015.ipynb

Run all rust-data · live

‹ All servers

Offline 118.178.196.247:28015 checked 1h ago

测试123456789

moddedoxide

Connect

srv = rust.server("118.178.196.247:27015")
print(srv.connect_command)

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 1 # peak 1
rank #4,753 # top 21%
last wipe 7h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75121:0005:0014:0023:0008:0018:00Wiped Thu 29 Oct, 13:34 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040021:0005:0014:0023:0008:0018: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 13:34 UTC7h ago NaN NaN running 1
1 Tue 27 Oct, 03:08 UTC2d ago 1+1 queue held half 2.4 days 0
2 Mon 26 Oct, 03:43 UTC3d ago 1 NaN 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.

display(srv.map, srv.info())

Map

3500 · seed 1573025114
Map of 测试123456789
map
Procedural Map
size
3500
seed
1573025114
Open on RustMaps

Server

srv.info()
address
118.178.196.247:28015
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 13:34 UTC
hostname
–
first seen
25 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 25 on average31/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 21 on average30/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average0/100
3[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 12 on average16/100
4[霸道]10000000倍-10.29日-萌新首选-稳定长久EA · no group limit · 12 on average17/100
5#10-[搞就完了]10倍/10.29新档/无权/萌新首选EA · no group limit · 12 on average19/100

Quick answers

From the figures on this page.

Population

How does 测试123456789 compare in the rankings?

Player hours over seven days put 测试123456789 at #4,753, in the top 21% of the ranked set.

How many players does 测试123456789 hold at once?

测试123456789 returns no live count at this refresh, having last been seen 1 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 03:00 UTC is the busiest, at 1 players.

Server facts

How smoothly does 测试123456789 run?

Server fps over the last 48 hours averages 159; the floor is 108. Buildings, deployables and all else in the world took the count as high as 77,576 entities. The memory field tops out at 3,251 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does 测试123456789 run?

Rust network protocol 2635 and build 168909 on Windows is what 测试123456789 runs. The protocol has to match before you can join, and Steam does the updating.

Is 测试123456789 up, and what does its uptime show?

The latest sample has 测试123456789 offline, with a last sighting 1 hours ago. Count back 2 hours from its reported uptime to get the last restart. Over the last 3 full days the hours up number 70 of 72, 97%. Rust Data logged it first on 25 October 2026.

Where does 测试123456789 sit?

Its name points to Asia, but 测试123456789 publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 118.178.196.247:28015 is its address.

Settings and map

Which settings and rules does 测试123456789 run?

No gather rate appears in the name: 测试123456789. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC off.

What is the map on 测试123456789?

Size 3,500, seed 1573025114: the procedural map on 测试123456789, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does 测试123456789 wipe, and on what schedule?

测试123456789 wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 7 hours ago.

What is wipe day on 测试123456789 like?

Across recent wipes the busiest point averaged 1 players. A peak 1 hours into the latest wipe, plus 1 waiting in the queue. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold 测试123456789, and which filters?

On Rust Data, 测试123456789 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on 测试123456789 hold?

Read by the game's server browser, the tags 测试123456789 publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way into 测试123456789?

The manual route: launch Rust, F1, then client.connect 118.178.196.247:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp1
Max players Slot count: 1.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 98,341 players 11,847 servers online