Rust Data

rustdata.spaceservers157.85.86.244:28016.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.86.244:28015 checked 11m ago

312c

moddedoxide

Connect

srv = rust.server("157.85.86.244:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/1 # 0% full
7-day average 0 # peak 1
rank #9,065 # top 41%
last wipe 3d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020022:0007:0016:0002:0011:0020: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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 41% 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 gap18.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sat 24 OctFri 2 OctFri 18 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 24 Oct, 20:52 UTC3d ago 1 NaN running 0
1 Fri 2 Oct, 06:29 UTC25d ago 0 NaN 22.6 days 0
2 Fri 18 Sep, 16:48 UTC39d ago 1 halved by day 1 13.6 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.

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

Map

5000 · seed 764331037
Map of 312c
map
Procedural Map
size
5000
seed
764331037
Open on RustMaps

Server

srv.info()
address
157.85.86.244:28015
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 21:31 UTC
hostname
–
first seen
17 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average119/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average131/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average119/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average27/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average114/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average34/1000

Quick answers

From the figures on this page.

Population

What position does 312c take in the server rankings?

Over the last seven days 312c sits at #9,065 on player hours, in the top 41% of ranked servers.

What population does 312c carry?

Current row: 0 players on 312c, against 1 slots. Over the last seven days it averaged 0 players and peaked at 1.

About the server

How well does 312c perform?

Server fps over the last 48 hours averages 78; the floor is 30. Buildings, deployables and all else in the world took the count as high as 145,531 entities. The memory field tops out at 5,341 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is 312c on?

The build is Rust network protocol 2635 and build 168909 on Linux, run by 312c. The protocol has to match before you can join, and Steam does the updating.

Is 312c up, and what does its uptime show?

Online is the state at the latest refresh for 312c. A restart about 20 hours ago is what its reported uptime implies. Uptime of 31% across the last 7 full days: 52 hours of 168. Rust Data logged it first on 17 September 2026.

In which location is 312c hosted?

No region is published by 312c. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.86.244:28015 is its address.

Settings and map

Which settings and rules does 312c run?

The name 312c carries no gather rate. 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. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on 312c?

Size 5,000, seed 764331037: the procedural map on 312c, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does 312c wipe, and how often?

No next wipe can be predicted for 312c, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 3 days ago.

On 312c, what happens on wipe day?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 2 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags, lists

Which lists on Rust Data hold 312c, and which filters?

These Rust Data lists include 312c: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on 312c hold?

Read by the game's server browser, the tags 312c publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; 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): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to 312c?

In Rust, F1 opens the console: type client.connect 157.85.86.244:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

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 1 slots in total.
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 Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 73,203 players 11,808 servers online