# Strange behavior with a date time in N8N

**URL:** <https://community.fibery.io/t/strange-behavior-with-a-date-time-in-n8n/11001>\
**Category:** API & Programming\
**Created:** [June 24, 2026, 2:15pm UTC](https://community.fibery.io/t/strange-behavior-with-a-date-time-in-n8n/11001 "2026-06-24T14:15:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene\_Vabishchevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eugene_vabishchevich/32/4310_2.png) [@Eugene\_Vabishchevich](https://community.fibery.io/u/Eugene_Vabishchevich)\
**Post date:** [June 24, 2026, 2:15pm UTC](https://community.fibery.io/t/strange-behavior-with-a-date-time-in-n8n/11001/1 "2026-06-24T14:15:02Z")

</div>

Hi guys! We use N8N Fibery node to create new record. We’ve set a formula for date time field as {{ $now.setZone(‘UTC’).toISO() }}. N8N shows it as “2026-06-24T14:13:00.136Z” but we receive a wrong hours number “24.06.2026 21:11”. Any ideas why? See screenshots attached

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/edc7df122f5dce247c0e6dc097e1435b825eec45.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/14de9f83114ebba397ae405234c2d2dbfdb2e6ee.png)

.