Interpret a UUID
Back
Your input: 9f00802f-1a05-8c02-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9f00802f-1a05-8c02-87ea-5ce32bd83b97
URI: uuid:9f00802f-1a05-8c02-87ea-5ce32bd83b97
Microsoft GUID syntax: {9F00802F-1A05-8C02-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9f00802f, 0x1a05, 0x8c02, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.211349851210007845438391332030205410199
As OID (Microsoft): 1.2.840.113556.1.8000.2554.40704.32815.6661.35842.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11457298391818931202.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2667610159.436571138.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.40704.32815.6661.35842.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9f00802f1a05c0207ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9f00802f]
Custom data block2 (16 bit): [0x1a05]
Custom data block3 (12 bit): [0xc02]
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: [0x9f00] 0b1001111100000000
Milliseconds: [0x80] 501 (deviation -2ms..2ms)
Seconds: [0x2f] 47
Minute of day: [0x051a] 1306 (21:45)
Day of year: [0x02c] 44 (Day=13, 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-13 21:45:47'501 (deviation -2ms..2ms)