Interprete a UUID

Back

UUID: 
Your input:                      5583151d-8600-8316-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:5583151d-8600-8316-87e9-5ce32bd83b97
URI:                             uuid:5583151d-8600-8316-87e9-5ce32bd83b97
Microsoft GUID syntax:           {5583151D-8600-8316-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x5583151d, 0x8600, 0x8316, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.113664998799875911576597113997719255959
As OID (Microsoft):              1.2.840.113556.1.8000.2554.21891.5405.34304.33558.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.6161791931719385878.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.1434653981.2248180502.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.21891.5405.34304.33558.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x5583151d860031607e95ce32bd83b97]
Custom data block1 (32 bit):     [0x5583151d]
Custom data block2 (16 bit):     [0x8600]
Custom data block3 (12 bit):     [0x316]
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:                  [0x5583] 0b0101010110000011
Milliseconds:                    [0x15] 82 (deviation -2ms..2ms)
Seconds:                         [0x1d] 29
Minute of day:                   [0x0086] 134 (02:13)
Day of year:                     [0x163] 355 (Day=21, 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-21 02:13:29'082 (deviation -2ms..2ms)