Interpret a UUID

Back

Your input:                      fdcc9d3b-3c03-8d00-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:fdcc9d3b-3c03-8d00-87ea-5ce32bd83b97
URI:                             uuid:fdcc9d3b-3c03-8d00-87ea-5ce32bd83b97
Microsoft GUID syntax:           {FDCC9D3B-3C03-8D00-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xfdcc9d3b, 0x3c03, 0x8d00, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.337357100524067575564943260341052652439
As OID (Microsoft):              1.2.840.113556.1.8000.2554.64972.40251.15363.36096.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.18288165064580238592.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.4258045243.1006865664.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.64972.40251.15363.36096.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xfdcc9d3b3c03d0007ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xfdcc9d3b]
Custom data block2 (16 bit):     [0x3c03]
Custom data block3 (12 bit):     [0xd00]
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:                  [0xfdcc] 0b1111110111001100
Milliseconds:                    [0x9d] 615 (deviation -2ms..2ms)
Seconds:                         [0x3b] 59
Minute of day:                   [0x033c] 828 (13:47)
Day of year:                     [0x00d] 13 (Day=13, 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-13 13:47:59'615 (deviation -2ms..2ms)