Rust Server Score · Report for the term · marked 30 October 2026 Pupil no. 213.246.39.157:27116

Name of server

RustMapEdit map test (not for play)

RegisterAbsent

Region–

Address213.246.39.157:27116

Last checked10d ago

Launch Rust and join

Overall grade

Not there yet

38 out of 100, the average of 2 subjects

Players now 0/ 2 0% full

7-day average0peak –

Rank#15,310top 70%

Last wipe10d agono schedule published

Next wipe–too few wipes seen yet

Subject	Mark	Teacher's comment
Populationplayers against slots, 7-day average	unmarked	No weekly average to mark yet.
Standingrank on player hours	30/ 100	Working its way up from the back of the class: #15,310 on player hours.
Uptimehours on the list, last 48	unmarked	Not seen long enough to take a register.
Performanceserver fps, last 48 hours	unmarked	Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe	unmarked	Too few wipes seen to mark this yet.
Momentumrank now against a week ago	47/ 100	Slipped a little: down 863 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in momentum (D); standing is the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

No hourly history yet.

Hourly average and peak, UTC.

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

Rank

daily · 1 is best

RankRank in region

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

Attendance: the wipe record

1 wipe day in the last 16 weeks

·······

W······

·····

W wiped that day F the force wipe · today. From the wipes in the table below.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

Wipes

newest first

Wiped	Peak	Crowd	Lasted	Players before
Mon 19 Oct, 07:36 UTC10d 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.

Similar servers

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

Rusty Moose |EU Mondays|

EU · groups of 12+ · weekly · 491 on average

72 / 250

Rustoria.co - EU East Long

EU · groups of 12+ · monthly · 319 on average

102 / 200

Rusty Moose |EU Main|

EU · groups of 12+ · weekly · 284 on average

314 / 350

Rustafied.com - EU Friday

EU · groups of 16+ · weekly · 277 on average

16 / 100

Rustoria.co - EU Main

EU · groups of 16+ · weekly · 266 on average

394 / 450

Rustoria.co - EU East Medium

EU · groups of 12+ · biweekly · 253 on average

291 / 325

Quick answers

from the figures on this page

Server details

In what location does RustMapEdit map test (not for play) sit?

No region is published for RustMapEdit map test (not for play). Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 213.246.39.157:27116.

How reliable is RustMapEdit map test (not for play), and is it up?

You cannot join now: RustMapEdit map test (not for play) is offline, last seen 10 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 15 October 2026.

What Rust version is RustMapEdit map test (not for play) on?

You will find RustMapEdit map test (not for play) on Rust network protocol 2634 and build 167781, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.

Wipe cycle

How frequently does RustMapEdit map test (not for play) wipe its map?

There are too few wipes on record for RustMapEdit map test (not for play) to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 10 days 18 hours have passed since this world was made.

What happens on RustMapEdit map test (not for play) when wipe day arrives?

Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began.

Player numbers

Where does RustMapEdit map test (not for play) sit among Rust servers?

Over the last seven days, RustMapEdit map test (not for play) has #15,310 for player hours, in the top 70% of all ranked servers.

How many players does RustMapEdit map test (not for play) usually have?

RustMapEdit map test (not for play) is offline at the moment; the last time it was seen was 10 days 16 hours ago.

Tags and filters

What do RustMapEdit map test (not for play)'s tags stand for?

You'll see RustMapEdit map test (not for play) tagged with gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.

Where does RustMapEdit map test (not for play) appear in the Rust Server Score lists and filters?

These Rust Server Score lists count RustMapEdit map test (not for play) among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules and settings

How is RustMapEdit map test (not for play) set up, and what rules does it keep?

The name of RustMapEdit map test (not for play) gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.

RustMapEdit map test (not for play) runs which map?

A procedural map of size 3,000 and seed 1337, generated by the game, is what RustMapEdit map test (not for play) runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.

Getting in

How should you connect to RustMapEdit map test (not for play)?

To connect, start Rust, press F1, and type client.connect 213.246.39.157:27116. Or click Launch Rust here, which launches Rust through Steam and joins you.

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8

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.