Interpret a UUID
Back
Your input: 39956d18-7b01-8108-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:39956d18-7b01-8108-87ea-5ce32bd83b97
URI: uuid:39956d18-7b01-8108-87ea-5ce32bd83b97
Microsoft GUID syntax: {39956D18-7B01-8108-87EA-5CE32BD83B97}
C++ struct syntax: { 0x39956d18, 0x7b01, 0x8108, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.76541860713853066923077402211143662487
As OID (Microsoft): 1.2.840.113556.1.8000.2554.14741.27928.31489.33032.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4149342583602118920.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.966094104.2063696136.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.14741.27928.31489.33032.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x39956d187b0110807ea5ce32bd83b97]
Custom data block1 (32 bit): [0x39956d18]
Custom data block2 (16 bit): [0x7b01]
Custom data block3 (12 bit): [0x108]
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: [0x3995] 0b0011100110010101
Milliseconds: [0x6d] 427 (deviation -2ms..2ms)
Seconds: [0x18] 24
Minute of day: [0x017b] 379 (06:18)
Day of year: [0x081] 129 (Day=9, Month=5)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-05-09 06:18:24'427 (deviation -2ms..2ms)