Interprete a UUID

Back

UUID: 
Your input:                      ef6ace23-9d03-860e-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ef6ace23-9d03-860e-87e9-5ce32bd83b97
URI:                             uuid:ef6ace23-9d03-860e-87e9-5ce32bd83b97
Microsoft GUID syntax:           {EF6ACE23-9D03-860E-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xef6ace23, 0x9d03, 0x860e, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.318240055457557031980559871162866744215
As OID (Microsoft):              1.2.840.113556.1.8000.2554.61290.52771.40195.34318.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.17251827974949537294.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4016754211.2634253838.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.61290.52771.40195.34318.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xef6ace239d0360e07e95ce32bd83b97]
Custom data block1 (32 bit):     [0xef6ace23]
Custom data block2 (16 bit):     [0x9d03]
Custom data block3 (12 bit):     [0x60e]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3

Random 16 bits:                  [0xef6a] 0b1110111101101010
Milliseconds:                    [0xce] 807 (deviation -2ms..2ms)
Seconds:                         [0x23] 35
Minute of day:                   [0x039d] 925 (15:24)
Day of year:                     [0x0e6] 230 (Day=18, Month=8)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-08-18 15:24:35'807 (deviation -2ms..2ms)