Interprete a UUID

Back

UUID: 
Your input:                      0a47e508-c404-8b15-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:0a47e508-c404-8b15-87e9-5ce32bd83b97
URI:                             uuid:0a47e508-c404-8b15-87e9-5ce32bd83b97
Microsoft GUID syntax:           {0A47E508-C404-8B15-87E9-5CE32BD83B97}
C++ struct syntax:               { 0x0a47e508, 0xc404, 0x8b15, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.13665578401094222271683817921872149399
As OID (Microsoft):              1.2.840.113556.1.8000.2554.2631.58632.50180.35605.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.740812489536867093.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.172483848.3288632085.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.2631.58632.50180.35605.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0x0a47e508c404b1507e95ce32bd83b97]
Custom data block1 (32 bit):     [0x0a47e508]
Custom data block2 (16 bit):     [0xc404]
Custom data block3 (12 bit):     [0xb15]
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:                  [0x0a47] 0b0000101001000111
Milliseconds:                    [0xe5] 897 (deviation -2ms..2ms)
Seconds:                         [0x08] 8
Minute of day:                   [0x04c4] 1220 (20:19)
Day of year:                     [0x15b] 347 (Day=13, 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-13 20:19:08'897 (deviation -2ms..2ms)