Interpret a UUID

Back

UUID: 
Your input:                      ed7a690c-9101-8e01-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:ed7a690c-9101-8e01-87ea-5ce32bd83b97
URI:                             uuid:ed7a690c-9101-8e01-87ea-5ce32bd83b97
Microsoft GUID syntax:           {ED7A690C-9101-8E01-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xed7a690c, 0x9101, 0x8e01, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.315662625866389850399645263050550295447
As OID (Microsoft):              1.2.840.113556.1.8000.2554.60794.26892.37121.36353.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.17112105236840943105.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3984222476.2432798209.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.60794.26892.37121.36353.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xed7a690c9101e0107ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xed7a690c]
Custom data block2 (16 bit):     [0x9101]
Custom data block3 (12 bit):     [0xe01]
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:                  [0xed7a] 0b1110110101111010
Milliseconds:                    [0x69] 411 (deviation -2ms..2ms)
Seconds:                         [0x0c] 12
Minute of day:                   [0x0191] 401 (06:40)
Day of year:                     [0x01e] 30 (Day=30, 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-30 06:40:12'411 (deviation -2ms..2ms)