Skip to main content
Palworld Metrics: Your Server's History and Player Statistics - visual guide

Palworld Metrics: Your Server's History and Player Statistics

What GameGrid Metrics records on a Palworld server and where each figure comes from: players online, uptime and restarts, sessions and playtime, Pals captured and bosses defeated, travel and bases, chat, building, server FPS and frame time, entities, ping, leaderboards, Discord and the API.

Where Metrics is

Open your server and click Metrics in the sidebar, just below Events. It is there in every state, stopped servers included, and a deactivated server keeps it so you can still read its history.

Metrics is yours. Only you and the people you give panel access to can see it, and nothing on the page is shown to your players unless you switch it on (see "Privacy" below).

On a Palworld server it answers what owners usually want to know. Is the server slowing down the longer it runs? When is everyone actually online? Which guild base do people spend their evenings at? Who has caught the most Pals and beaten the most bosses?

On a Palworld server the page has these tabs:

TabWhat it is for
OverviewThe headline cards: players online, resources, server health, busiest hours, and the player cards
PlayersEvery player ranked by playtime, distance and more, plus Leaderboards
SessionsEvery session: who joined, when, for how long, and how far they went
PlacesYour players' bases and the map's grid squares, by time spent
TravelYour live map with density and trails, plus distance and speed
EventsEvent Manager and Command Manager runs, prize events, stops and crashes
EconomyCoins earned and spent, purchases and deliveries (servers that use the GameGrid economy)
ActivityOne timeline of chat, commands, Pal captures, technology unlocks, building, joins and leaves, purchases and moderation
HealthUptime, outages, start times, CPU, memory, network, disk, server FPS, frame time, entities, ping and bases
Busiest hoursA weekday-by-hour grid of when players are on
SettingsThe Overview layout, Import history from logs, stats seasons, Player access and alerts

Metrics shows no deaths or kills on Palworld, so a Palworld server has no Combat tab, no deaths cards and no Kills today tile. Each player's profile has a Combat tab instead with their Palworld progress (see "Pals, bosses and progress" below).

The general guide to every card, range and button is Metrics: Your Server's History. This article covers what is specific to Palworld.

How GameGrid collects Palworld data

Palworld Metrics reads the server's own log, its REST API, and PalDefender, which GameGrid installs and repairs with UE4SS on every Palworld server start (the UE4SS tab of Palworld Game Tools).

WhatWhere it comes from
Server history: running, stopped, crashed, restarts and their causes, CPU, memory, network, disk, players onlineGameGrid's own monitoring of the server, for every game
Joins, leaves and sessionsThe server log's joined and left lines
Positions (travel, trails, density, places)The REST API's player list, the same reading the live map uses, every 30 seconds. Palworld positions are drawn flat, without height
Chat and commandsPalDefender's chat lines in the server log
Pal captures and technology unlocksPalDefender's lines in the server log
Building and dismantlingPalDefender's lines in the server log
Pals captured, bosses, dungeons, crafts, fishing and treasure countersPalDefender's own progress record for each online player, every 5 minutes
Server FPS, frame time, base camps and the in-game dayThe REST API's server metrics
Players' pingThe REST API's player list
EntitiesPalworld's GameData API, every 5 minutes

The REST API's player list also carries each player's address. Metrics never reads it, apart from the one-way code described under "Moderation" below.

Who a player is on Palworld

A player who plays on Steam is identified by their Steam ID, so one person stays one player whatever their character is called. A player on Xbox, PlayStation or another platform has no Steam ID and is identified by their Palworld user id instead, which is just as lasting.

On a player's profile, the account owner and administrators see the Steam ID with a Copy button; the search box in the player list accepts a name, a character name or a Steam ID.

The Overview

CardWhat it shows on Palworld
Players onlineThe highest player count in each interval, the peak and when it happened, the average, and how much of the running time the server was empty
ResourcesCPU and memory while the server ran, how long it ran, and how long it has been up now
Server healthWhen the server was running, starting, stopped, crashed or unreachable, with every crash and restart marked and named by its cause
Busiest hoursWeekdays by hours in your time zone, darker where more players were on
Top playersYour top five by playtime
Player engagementUnique and new players per interval
Session durationThe average session length, the median and the longest
Logins per daySessions started each day
Top places and TravelThe bases and grid squares players spent most time in, and distance per day
Chat & commandsMessages and commands per day and the most active chatter
Event historyThe latest five events
BuildingBuild actions per day and your top builders
EconomyCoins earned and spent per day, on servers that use the GameGrid economy

Untick or reorder cards on the Settings tab, or with โš™ Layout at the top of the page.

Server health, uptime and restarts

The Server health summary reads like "Availability 96.4% ยท Uptime when meant to be on 99.1% ยท 1 crash ยท 3 restarts (2 scheduled, 1 Event Manager)".

  • Availability is the share of the range the server was running.
  • Uptime when meant to be on leaves out the time you meant it to be off: after you stop the server yourself, that time does not count against it until you start it again.
  • Every restart is named by its cause: Owner (you, from the panel, the API or the Discord bot), Scheduled restart, Event Manager, Command Manager, Update or move, Crash recovery, Exited by itself, Crash, Host unreachable, Deactivated, or Other when nothing recorded why.
  • A grey band labelled REST API unavailable: player data unknown marks minutes the server ran but its REST API did not answer, so who was on is not known for those minutes. It is not "nobody played". A minute or two of it while the world loads is normal.

The Health tab adds Availability per day, Outages (every stretch the server was meant to be on but was not), Time to ready (how long starts take, on average and for nine starts in ten), CPU, Memory, Network, Disk used, Backups and Game updates and mods.

Performance: FPS, frame time, entities, ping and bases

Palworld's REST API reports the server's own frame rate, frame time, base count and in-game day, and the Health tab draws them next to CPU and memory.

  • FPS is how many times a second the server updates the world. The useful question is not "what is the number" but "does it hold". Compare a busy evening with a quiet afternoon: if FPS drops as players log in and recovers when they leave, the server is busy; if it keeps sliding the longer the server has been up, see below.
  • Frame time is the same thing from the other side: how long one update takes, in milliseconds. It rises when FPS falls.
  • Entities is the Pals, NPCs and other actors the GameData API reports. Busy bases full of working Pals push it up.
  • Player ping is the average ping of the connected players. If one player complains and the average is fine, it is their connection.
  • Bases over time is how many base camps the world holds, which climbs as guilds settle in.

An FPS line that sinks while the Memory line climbs over a long uptime, and recovers after a restart, is the pattern described in Palworld Server Memory Leak and High RAM Usage. A regular restart from your auto-restart policy is the usual answer. Ping is measured only while players are connected.

Busiest hours

The Busiest hours tab shows the grid at full size. Switch between Average players and Peak players, Unique players and New players, and tick Include offline time to count the hours the server was off as empty. Below it are your Top 5 slots and Best time for an event, which opens the Event Manager with that time filled in.

Players, sessions and profiles

The ๐Ÿ‘ฅ Players button opens a list of everyone who has played on your server; the Players tab ranks them (Rank, Player, Logins, Playtime, Distance, Last active), and the Sessions tab lists every session with its length and distance. Each name opens the player's profile: playtime, sessions, distance, places discovered, the names they used, where they spend time and their latest activity. Full detail: Metrics: Player List and Player Profiles.

Import history from logs (on the Settings tab) reads the Palworld logs still on your server once, up to 30 days back, and adds the sessions they record from before player statistics started. Running it again adds nothing new.

Pals, bosses and progress

Every 5 minutes, for each player online, GameGrid asks PalDefender for that player's lifetime progress and keeps it on their profile's Combat tab: Pals captured, Bosses defeated, Tower bosses defeated, Dungeons cleared, Oil rigs cleared, Items crafted, Fish caught and Treasures found. These are Palworld's own counters for the character, so they include progress made before GameGrid started recording. A player who has caught a few hundred Pals and cleared the towers will show those numbers the first time they log in. The figures refresh while the player is online, so someone who has not played since recording began has none.

Each Pal a player captures and each technology they unlock also appears on the Activity tab under World events, with the Pal or the technology named.

Travel and places

Travel shows your server's own live map with Density and Trails layers. Pick all players, up to 20, or one player's session, and press Play to replay the trails. Beside the map: total distance, time moving and idle, average and top speed, the top travellers and distance per day.

A place on Palworld is:

  • Bases: each Pal Box base, named after its guild ("Guild base");
  • Grid: the lettered and numbered squares the live map draws.

A guild that builds two or three bases, one by the ore and one by the farm, will see each one listed, with how long members spend at each. Places ranks them by time spent, visits or visitors and opens each one: time spent per day, its busiest hours, who spends most time there and who visited first. Positions older than 30 days are kept only as each session's simplified path and as time per grid square.

Events, economy, activity, building and chat

  • Events lists Event Manager settings windows, Command Manager runs, prize events, and the server's stops and crashes. Open a row to see who took part.
  • Activity is one timeline of chat, commands, Pal captures and technology unlocks, building, joins and leaves, purchases, moderation and the server's own history, with filters and a search.
  • Chat is the in-game chat, as PalDefender writes it into the server log. A line starting with ! or / is filed as a command. The password in /AdminPassword <password> is never stored: the line reads /AdminPassword [hidden].
  • Building comes from PalDefender: each structure a player builds or dismantles, named. The Build filter on the Activity tab shows every one.
  • Economy shows coins earned and spent, how coins are earned, how wealth is spread, the items bought most beside how each delivery ended, the richest players (named only to the server's owner and administrators), kits and refunds, on a server that uses the GameGrid economy. See Palworld Economy and Item Delivery.

Only the server's owner and administrators can read chat text. Everyone else sees that a message was sent, not what it said.

The live status bar

The server's Overview page and the Metrics page show a status bar. On Palworld it can show: Status, Players online, FPS (with a line of the last 15 minutes), Entities, Uptime, Server time with the in-game day under it, Next restart, Ping, Uptime when on (7 d) and Peak today. Press โš™ to choose and order them. While the server is stopped the game figures say not running.

Ranges, time zones, tables and downloads

  • The bar at the top picks the range: Live (the last 15 minutes, refreshed every 10 seconds), 1h, 24h, 7d, 30d, 90d or your own dates. Granularity sets how wide each step of a chart is, and Compare to previous period draws the period before as a dashed line with the change beside each headline number.
  • Every time is shown in your own time zone, named in the bar; the change link goes to your account page.
  • Show as table on any card swaps the chart for the same figures as a table. The card's โ‹ฏ menu has Download CSV, and Export downloads every card on the tab.
  • The detailed record goes back seven days; before that charts are filled from hourly records and say "Hour-grained before" and the date.

Privacy: what is recorded about your players

  • Player statistics are recorded from 6 October 2026, when version 1.1.0 of GameGrid's Privacy Policy took effect. Apart from sessions added with Import history from logs and the lifetime counters PalDefender keeps, nothing about players was recorded before that, and a chart that reaches further back marks where recording began with Not recorded before and the date. The server's own history (uptime, restarts, CPU, memory, players online) goes back further.
  • Player IP addresses are never shown or stored by Metrics: not on any page, in any download, in the API or in the Discord bot. PalDefender writes them into its log lines, and GameGrid removes them before a line is read.
  • Player access (Metrics, Settings) decides what your players can see. Every switch is off until you turn it on: live positions on share links, leaderboards, posts to Discord and player self-service.
  • Forget this player, on a player's profile under Admin, deletes their positions, places and names from Metrics on all your servers and keeps their statistics as "Deleted player", so your totals stay right.
  • Positions are kept 30 days, sessions 365 days, chat 180 days.
  • Resetting the world keeps every statistic. Start a new stats season when you want a fresh start: Metrics: Stats Seasons and Wiping Player Stats.

Full detail: Metrics and Your Players' Privacy.

Moderation and possible alternative accounts

On a Palworld server Metrics can suggest that two players may be the same person: linked to the same Discord account, the same game account, or connecting from the same connection, which the machine your server runs on reads from the REST API's player list and turns into a one-way code at once. The address itself is never kept. A suggestion is a hint, never proof, and nothing is done automatically. You can also put a player On Watch, keep notes and set Alerts (a watched player connects, a chat keyword). See Metrics: Moderation, Possible Alternative Accounts and On Watch.

Discord: /metrics, /leaderboard and /my

Your GameGrid Discord bot reads Metrics with the server's API key. Create that key with the Discord bot preset, which includes the Metrics read scopes (Discord Bot Setup).

  • `/metrics` for your staff: summary, uptime and peak (which may be posted in the channel), top, player, places and sessions (always private), and new-season. The moderation subcommands alts and watch need the player_metrics:alts and player_metrics:write scopes added to the bot's key, which the preset leaves out. On Palworld, /metrics top can rank by Playtime, Distance, Sessions or Logins, and /metrics summary adds a performance line with FPS, frame time and entities.
  • `/leaderboard` for everyone, once you switch it on. A Palworld server is offered Playtime, Distance travelled, Places discovered, Event wins and the Milestones feed, plus Top earners and Wealth with the GameGrid economy. Turn on Posted leaderboards or the /leaderboard command under Metrics, Settings, Player access, then set each board up in Players โ†’ Leaderboards or with /leaderboard setup. See Metrics Leaderboards.
  • `/my` lets a player read their own statistics: /my stats, /my playtime, /my travel, /my wealth, /my events. Switch on Discord /my and tick the sections to share under Metrics, Settings, Player access, Player self-service. Players must link their Discord with /link and !link in game chat first. See Player Self-Service.

The Customer API

Everything on the Metrics page is in the Customer API too: server history, busiest hours, places, players, sessions and CSV downloads. Server history needs the metrics:read scope and player data player_metrics:read. See Customer API and API Scopes.

Troubleshooting

  • No Players, Sessions or Travel tab. These appear once player statistics are recorded and someone has played since. If the page shows "Player recording starts" with a date, they appear from then.
  • A card says "No ... between" two dates. Nothing happened in that range, or the server was not running then. Try a longer range with Widen to 90 days.
  • "REST API unavailable: player data unknown" on Server health. Who is online and where comes from the REST API, which GameGrid switches on at every start (Palworld REST API Guide). A short stretch while the world loads is normal; if it lasts while the server runs, restart it, and contact support if it stays.
  • No chat, captures, building or progress. These come from PalDefender. If you took the mod stack off on the UE4SS tab, put it back with Install Everything and restart the server.
  • No Entities chart. Entities come from the GameData API, which GameGrid switches on at every start; the live map's Enable GameData API button turns it back on if it was turned off.
  • There is no Combat tab. Metrics shows no deaths or kills on Palworld; a player's progress is on their profile's Combat tab.