---
name: "serverTime"
type: command
status: ok
groups: ["Time", "Mission Information", "Multiplayer"]
arma3_since: "0.50"
locality: {"argument": null, "effect": "global", "server_exec": false}
source: https://community.bistudio.com/wiki/serverTime
revid: 364976
updated: 2024-07-04T17:33:25Z
---

# serverTime

*Command · Time, Mission Information, Multiplayer · Arma 3 v0.50 · introduced in Arma 2 v1.00*

Locality: effect **global**

## Description

Returns the time since latest server (re)start in seconds.

> [!IMPORTANT]
> The time returned is different to the time returned by [time](../commands/time.md) and [diag_tickTime](../commands/diag_tickTime.md) commands on server.

> [!NOTE]
> Known issues before Arma 3 v1.86:
> both server and clients showed the same value when synced, but the only time it was not synced was on the server, right after server restart and only for the first 300 seconds. Client-side it was synced from the start.

## Syntax

```sqf
serverTime
```

**Returns:** [Number](../topics/Number.md)

## Examples

### Example 1

```sqf
hint format ["Synced server time : %1", serverTime];
```

## Multiplayer

- In singleplayer: Arma 3 v2.18 returns the same value as [diag_tickTime](../commands/diag_tickTime.md), the time since game launch (returned 0 before v2.18)
- In multiplayer: It is synced to all clients both at mission start and when a new client connects to it, and every 5 minutes. Synchronisation can be forced by executing the [estimatedTimeLeft](../commands/estimatedTimeLeft.md) command.

## See also

[time](../commands/time.md) · [diag_tickTime](../commands/diag_tickTime.md) · [date](../commands/date.md) · [missionStart](../commands/missionStart.md) · [estimatedTimeLeft](../commands/estimatedTimeLeft.md) · [estimatedEndServerTime](../commands/estimatedEndServerTime.md) · [systemTime](../commands/systemTime.md) · [systemTimeUTC](../commands/systemTimeUTC.md)

<sub>Source: [BI Community Wiki — serverTime](https://community.bistudio.com/wiki/serverTime) (revision 364976).</sub>