Interpret a UUID

Back

UUID: 
Your input:                      fa96b804-1b01-8a02-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:fa96b804-1b01-8a02-87ea-5ce32bd83b97
URI:                             uuid:fa96b804-1b01-8a02-87ea-5ce32bd83b97
Microsoft GUID syntax:           {FA96B804-1B01-8A02-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xfa96b804, 0x1b01, 0x8a02, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.333089575763646870258904494301517462423
As OID (Microsoft):              1.2.840.113556.1.8000.2554.64150.47108.6913.35330.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.18056822083761048066.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4204181508.453085698.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.64150.47108.6913.35330.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xfa96b8041b01a0207ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xfa96b804]
Custom data block2 (16 bit):     [0x1b01]
Custom data block3 (12 bit):     [0xa02]
Custom data block4 (14 bit):     [0x07ea]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xfa96] 0b1111101010010110
Milliseconds:                    [0xb8] 721 (deviation -2ms..2ms)
Seconds:                         [0x04] 4
Minute of day:                   [0x011b] 283 (04:42)
Day of year:                     [0x02a] 42 (Day=11, Month=2)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-02-11 04:42:04'721 (deviation -2ms..2ms)