Interpret a UUID
Back
Your input: 40cf0b36-2e01-850a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:40cf0b36-2e01-850a-87ea-5ce32bd83b97
URI: uuid:40cf0b36-2e01-850a-87ea-5ce32bd83b97
Microsoft GUID syntax: {40CF0B36-2E01-850A-87EA-5CE32BD83B97}
C++ struct syntax: { 0x40cf0b36, 0x2e01, 0x850a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.86145624579015888770203250730085137303
As OID (Microsoft): 1.2.840.113556.1.8000.2554.16591.2870.11777.34058.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4669963665934484746.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1087310646.771851530.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.16591.2870.11777.34058.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x40cf0b362e0150a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x40cf0b36]
Custom data block2 (16 bit): [0x2e01]
Custom data block3 (12 bit): [0x50a]
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: [0x40cf] 0b0100000011001111
Milliseconds: [0x0b] 43 (deviation -2ms..2ms)
Seconds: [0x36] 54
Minute of day: [0x012e] 302 (05:01)
Day of year: [0x0a5] 165 (Day=14, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-14 05:01:54'043 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing