Interpret a UUID

Back

UUID: 
Your input:                      30ea9605-7000-8001-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:30ea9605-7000-8001-87ea-5ce32bd83b97
URI:                             uuid:30ea9605-7000-8001-87ea-5ce32bd83b97
Microsoft GUID syntax:           {30EA9605-7000-8001-87EA-5CE32BD83B97}
C++ struct syntax:               { 0x30ea9605, 0x7000, 0x8001, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.65020984054817397477485096645812566935
As OID (Microsoft):              1.2.840.113556.1.8000.2554.12522.38405.28672.32769.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.3524794608468918273.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.820680197.1879080961.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.12522.38405.28672.32769.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x30ea9605700000107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0x30ea9605]
Custom data block2 (16 bit):     [0x7000]
Custom data block3 (12 bit):     [0x001]
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:                  [0x30ea] 0b0011000011101010
Milliseconds:                    [0x96] 588 (deviation -2ms..2ms)
Seconds:                         [0x05] 5
Minute of day:                   [0x0070] 112 (01:51)
Day of year:                     [0x010] 16 (Day=16, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-16 01:51:05'588 (deviation -2ms..2ms)