# Gateway timestamps in uplink metadata - how calculated?

**URL:** <https://www.thethingsnetwork.org/forum/t/gateway-timestamps-in-uplink-metadata-how-calculated/23703>\
**Category:** Application Development\
**Created:** [March 10, 2019, 3:40pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-timestamps-in-uplink-metadata-how-calculated/23703 "2019-03-10T15:40:11Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [January 22, 2020, 3:17pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-timestamps-in-uplink-metadata-how-calculated/23703/20 "2020-01-22T15:17:25Z")

</div>

> [@harofani](#):
>
> create an application where different LoRa devices are synchronised based on a time from TTN server

If you’re trying to make the nodes transmit at the same time: don’t. That will create network issues. Instead, the node should always apply some randomness when it wants to transmit something.

If you’re trying to make the nodes know the current time, then remember that a downlink is always RX1 or RX2 seconds after the uplink, which can be used to synchronize clocks with a time you create yourself, rather than relying on some timestamp generated by some network server. But beware that a downlink that is scheduled after some uplink might not be transmitted right away, so might be transmitted after _the next_ uplink, which you need to detect by including some counter. For all this, see [Time synchronisation of a Node](https://www.thethingsnetwork.org/forum/t/time-synchronisation-of-a-node/1641).

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/gateway-timestamps-in-uplink-metadata-how-calculated/23703)._
