IoT Protocol Timestamp Converter

Q: What is the CoAP timestamp format?

**32-bit unsigned seconds since 2000-01-01** (per RFC 7641/CoRE), wrapping in 2136. The converter outputs the integer.

Q: What is the LoRaWAN timestamp format?

UTC seconds, commonly **GPS-style (1980 epoch) or Unix (1970)** depending on the network server; the converter renders the Unix form.

Q: What is the Zigbee time format?

**UTC with 0.1-second resolution** since 2000-01-01, stored as 32-bit — a 0.1s tick count.

Q: What is the UEFI time format?

**100ns since 1601** (the same epoch as Windows FILETIME) — `EFI_TIME`/`EFI_TIME_CAPABILITIES` use this scale.

IoT protocols embed time compactly: CoAP (seconds since 2000), LoRaWAN (UTC seconds), Zigbee (UTC with 0.1s resolution), UEFI (100ns since 1601) and VxWorks (ticks). Devices across a fleet must agree on these scales for valid timestamps.

This converter renders your date-time in each IoT protocol representation for firmware development, packet building and sensor data analysis.

Timezone:

Enter a date-time above to see the conversion results.

IoT Protocol Timestamp Converter Quick Reference

Format	Pattern / Description	Example 1	Example 2
CoAP Option	RFC 7252	1786631400	1767225600
LoRaWAN GPS	Device Time	1470666600	1451260800
Zigbee Time	Standard Time	839946600	820540800
UEFI Time	EFI_TIME	2026-08-13 14:30:00	2026-01-01 00:00:00
VxWorks System	Ticks since boot	1786631400	1767225600

* Examples are rendered in UTC for the fixed sample instants above.

When to Use IoT Protocol Timestamp

Firmware development

Generate CoAP/LoRaWAN timestamp values for protocol unit tests and packet crafting.

Sensor fleet analysis

Convert raw Zigbee/CoAP timestamps from device payloads into wall-clock for data science.

Gateway integration

Build gateway logic that translates between protocol timestamps and UTC for cloud ingestion.

Frequently Asked Questions

What is the CoAP timestamp format?

32-bit unsigned seconds since 2000-01-01 (per RFC 7641/CoRE), wrapping in 2136. The converter outputs the integer.

What is the LoRaWAN timestamp format?

UTC seconds, commonly GPS-style (1980 epoch) or Unix (1970) depending on the network server; the converter renders the Unix form.

What is the Zigbee time format?

UTC with 0.1-second resolution since 2000-01-01, stored as 32-bit — a 0.1s tick count.

What is the UEFI time format?

100ns since 1601 (the same epoch as Windows FILETIME) — `EFI_TIME`/`EFI_TIME_CAPABILITIES` use this scale.

Related Time Format Converters

Windows FILETIME Converter

Convert dates to Windows FILETIME (100-ns ticks since 1601), OLE Automation dates and LDAP timestamps. Free converter for Windows and AD developers.

NTP Timestamp Converter

Convert dates to NTP timestamps: 64-bit NTP format (seconds + fraction since 1900) and hex representation. Free converter for network time debugging.

CAN Bus & AUTOSAR Timestamp Converter

Convert dates to CAN bus, AUTOSAR and RTOS tick timestamps. See raw tick counts and system time values. Free converter for embedded developers.

All Format Guides

Unix Timestamp ISO 8601 ISO Week Date ISO Ordinal Date Military Time Decimal Time RFC 2822 RFC 3339 SQL Datetime Julian Date HTTP Date Excel Serial Date GPS Time UTC Time Cron Expression

Browse all 50 format guides →

Need to Convert Between All Formats?

Use the main Time Format Converter for instant conversion across 100+ formats — epoch, ISO 8601, RFC 3339, SQL datetime, military time and more in one click.

Open Time Format Converter