Interpret a UUID
Back
Your input: 27596a0c-dd02-8d04-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:27596a0c-dd02-8d04-87ea-5ce32bd83b97
URI: uuid:27596a0c-dd02-8d04-87ea-5ce32bd83b97
Microsoft GUID syntax: {27596A0C-DD02-8D04-87EA-5CE32BD83B97}
C++ struct syntax: { 0x27596a0c, 0xdd02, 0x8d04, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.52304157210576526909835971887170599831
As OID (Microsoft): 1.2.840.113556.1.8000.2554.10073.27148.56578.36100.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.2835414043886521604.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.660171276.3707931908.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.10073.27148.56578.36100.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x27596a0cdd02d0407ea5ce32bd83b97]
Custom data block1 (32 bit): [0x27596a0c]
Custom data block2 (16 bit): [0xdd02]
Custom data block3 (12 bit): [0xd04]
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: [0x2759] 0b0010011101011001
Milliseconds: [0x6a] 415 (deviation -2ms..2ms)
Seconds: [0x0c] 12
Minute of day: [0x02dd] 733 (12:12)
Day of year: [0x04d] 77 (Day=18, Month=3)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-03-18 12:12:12'415 (deviation -2ms..2ms)