Interpret a UUID

Back

Your input:                      fe89fa16-1600-8c00-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:fe89fa16-1600-8c00-87ea-5ce32bd83b97
URI:                             uuid:fe89fa16-1600-8c00-87ea-5ce32bd83b97
Microsoft GUID syntax:           {FE89FA16-1600-8C00-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xfe89fa16, 0x1600, 0x8c00, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.338340327951217722691268020911807675287
As OID (Microsoft):              1.2.840.113556.1.8000.2554.65161.64022.5632.35840.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.18341465930208414720.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4270455318.369134592.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.65161.64022.5632.35840.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xfe89fa161600c0007ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xfe89fa16]
Custom data block2 (16 bit):     [0x1600]
Custom data block3 (12 bit):     [0xc00]
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:                  [0xfe89] 0b1111111010001001
Milliseconds:                    [0xfa] 979 (deviation -2ms..2ms)
Seconds:                         [0x16] 22
Minute of day:                   [0x0016] 22 (00:21)
Day of year:                     [0x00c] 12 (Day=12, Month=1)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-01-12 00:21:22'979 (deviation -2ms..2ms)