# Convert non-UTC timestamp to UTC

**URL:** <https://discourse.nodered.org/t/convert-non-utc-timestamp-to-utc/16092>\
**Category:** General\
**Created:** [30 September 2019 13:21 UTC](https://discourse.nodered.org/t/convert-non-utc-timestamp-to-utc/16092 "2019-09-30T13:21:59Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 October 2019 15:42 UTC](https://discourse.nodered.org/t/convert-non-utc-timestamp-to-utc/16092/13 "2019-10-01T15:42:15Z")

</div>

> [@mifrey](#):
>
> The timestamp 1569948710 = UTC Tuesday, October 1, 2019 4:51:50 PM. So that shows that the timestamp is not the UTC time

Yes, you are right. It is not possible to reliably convert from a timezone which may include DST to another timezone, as there are times when the ticks could represent two possible times (during the repeated hour). Have you tried contacting the supplier of the device and ask him to fix it?

---

_[View the full topic](https://discourse.nodered.org/t/convert-non-utc-timestamp-to-utc/16092)._