Interpret a UUID

Back

UUID: 
Your input:                      a23a090f-4305-8904-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:a23a090f-4305-8904-87ea-5ce32bd83b97
URI:                             uuid:a23a090f-4305-8904-87ea-5ce32bd83b97
Microsoft GUID syntax:           {A23A090F-4305-8904-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xa23a090f, 0x4305, 0x8904, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.215636272285802449326787456638031248279
As OID (Microsoft):              1.2.840.113556.1.8000.2554.41530.2319.17157.35076.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.11689665743947139332.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2721712399.1124436228.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.41530.2319.17157.35076.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xa23a090f430590407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xa23a090f]
Custom data block2 (16 bit):     [0x4305]
Custom data block3 (12 bit):     [0x904]
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:                  [0xa23a] 0b1010001000111010
Milliseconds:                    [0x09] 35 (deviation -2ms..2ms)
Seconds:                         [0x0f] 15
Minute of day:                   [0x0543] 1347 (22:26)
Day of year:                     [0x049] 73 (Day=14, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-14 22:26:15'035 (deviation -2ms..2ms)