Interpret a UUID
Back
Your input: 09aea419-0f00-8706-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:09aea419-0f00-8706-87ea-5ce32bd83b97
URI: uuid:09aea419-0f00-8706-87ea-5ce32bd83b97
Microsoft GUID syntax: {09AEA419-0F00-8706-87EA-5CE32BD83B97}
C++ struct syntax: { 0x09aea419, 0x0f00, 0x8706, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.12869839915971277381326107437283425175
As OID (Microsoft): 1.2.840.113556.1.8000.2554.2478.42009.3840.34566.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.697675419821836038.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.162440217.251692806.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.2478.42009.3840.34566.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x09aea4190f0070607ea5ce32bd83b97]
Custom data block1 (32 bit): [0x09aea419]
Custom data block2 (16 bit): [0x0f00]
Custom data block3 (12 bit): [0x706]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x09ae] 0b0000100110101110
Milliseconds: [0xa4] 642 (deviation -2ms..2ms)
Seconds: [0x19] 25
Minute of day: [0x000f] 15 (00:14)
Day of year: [0x067] 103 (Day=13, Month=4)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-04-13 00:14:25'642 (deviation -2ms..2ms)