Interpret a UUID
Back
Your input: 468c6b14-5c00-8a0f-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:468c6b14-5c00-8a0f-87ea-5ce32bd83b97
URI: uuid:468c6b14-5c00-8a0f-87ea-5ce32bd83b97
Microsoft GUID syntax: {468C6B14-5C00-8A0F-87EA-5CE32BD83B97}
C++ struct syntax: { 0x468c6b14, 0x5c00, 0x8a0f, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.93775053096003100861916163842277653399
As OID (Microsoft): 1.2.840.113556.1.8000.2554.18060.27412.23552.35343.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.5083555814581504527.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1183607572.1543539215.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.18060.27412.23552.35343.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x468c6b145c00a0f07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x468c6b14]
Custom data block2 (16 bit): [0x5c00]
Custom data block3 (12 bit): [0xa0f]
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: [0x468c] 0b0100011010001100
Milliseconds: [0x6b] 419 (deviation -2ms..2ms)
Seconds: [0x14] 20
Minute of day: [0x005c] 92 (01:31)
Day of year: [0x0fa] 250 (Day=7, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-07 01:31:20'419 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing