Interprete a UUID

Back

UUID: 
Your input:                      16f0a316-00f1-8076-87e8-5ce32bd83b96

Various notations:

URN:                             urn:uuid:16f0a316-00f1-8076-87e8-5ce32bd83b96
URI:                             uuid:16f0a316-00f1-8076-87e8-5ce32bd83b96
Microsoft GUID syntax:           {16F0A316-00F1-8076-87E8-5CE32BD83B96}
C++ struct syntax:               { 0x16f0a316, 0x00f1, 0x8076, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.30492474929393436142771518069005630358
As OID (Microsoft):              1.2.840.113556.1.8000.2554.5872.41750.241.32886.34792.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.1653000378145407094.9793179520480066454
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.384869142.15827062.2280152291.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.5872.41750.241.32886.34792.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x16f0a31600f107607e85ce32bd83b96]
Custom data block1 (32 bit):     [0x16f0a316]
Custom data block2 (16 bit):     [0x00f1]
Custom data block3 (12 bit):     [0x076]
Custom data block4 (14 bit):     [0x07e8]
Custom data block5 (48 bit):     [0x5ce32bd83b96]

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

Random 16 bits:                  [0x16f0] 0b0001011011110000
Milliseconds:                    [0xa3] 639 (deviation -2ms..2ms)
Seconds:                         [0x16] 22
Minute of day:                   [0x00f1] 241 (04:00)
Day of year:                     [0x076] 118 (Day=27, Month=4)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e8] 2024
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2024-04-27 04:00:22'639 (deviation -2ms..2ms)