Interprete a UUID

Back

UUID: 
Your input:                      af9d3333-d901-8016-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:af9d3333-d901-8016-87e9-5ce32bd83b97
URI:                             uuid:af9d3333-d901-8016-87e9-5ce32bd83b97
Microsoft GUID syntax:           {AF9D3333-D901-8016-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xaf9d3333, 0xd901, 0x8016, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.233431128379836381094101494527411370903
As OID (Microsoft):              1.2.840.113556.1.8000.2554.44957.13107.55553.32790.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.12654326825758064662.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.2946315059.3640754198.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.44957.13107.55553.32790.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xaf9d3333d90101607e95ce32bd83b97]
Custom data block1 (32 bit):     [0xaf9d3333]
Custom data block2 (16 bit):     [0xd901]
Custom data block3 (12 bit):     [0x016]
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:                  [0xaf9d] 0b1010111110011101
Milliseconds:                    [0x33] 200 (deviation -2ms..2ms)
Seconds:                         [0x33] 51
Minute of day:                   [0x01d9] 473 (07:52)
Day of year:                     [0x160] 352 (Day=18, Month=12)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-12-18 07:52:51'200 (deviation -2ms..2ms)