# Get the timezone

**URL:** <https://forum.inductiveautomation.com/t/get-the-timezone/30471>\
**Category:** Module Development\
**Created:** [December 5, 2019, 4:37pm UTC](https://forum.inductiveautomation.com/t/get-the-timezone/30471 "2019-12-05T16:37:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpark](https://avatars.discourse-cdn.com/v4/letter/j/a88e57/32.png) [@jpark](https://forum.inductiveautomation.com/u/jpark)\
**Post date:** [December 5, 2019, 4:37pm UTC](https://forum.inductiveautomation.com/t/get-the-timezone/30471/1 "2019-12-05T16:37:57Z")

</div>

I am implementing a HistoryQueryExecutor. How do I get the timezone? It could be different between client / designer / gateway.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 5, 2019, 5:46pm UTC](https://forum.inductiveautomation.com/t/get-the-timezone/30471/2 "2019-12-05T17:46:17Z")

</div>

You shouldn’t need it. The java.util.Date objects you get in any scope have already taken care of that. java.util.Date contains UTC milliseconds upon creation, and that absolute time is maintained through serialization (client-gateway RPC). The t\_stamp column in Ignition’s historian tables is UTC milliseconds as a long integer. You should do the same.