Interpret a UUID
Back
Your input: f40b5b2a-8c03-8001-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:f40b5b2a-8c03-8001-87ea-5ce32bd83b97
URI: uuid:f40b5b2a-8c03-8001-87ea-5ce32bd83b97
Microsoft GUID syntax: {F40B5B2A-8C03-8001-87EA-5CE32BD83B97}
C++ struct syntax: { 0xf40b5b2a, 0x8c03, 0x8001, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.324390595307152246637150963664462298007
As OID (Microsoft): 1.2.840.113556.1.8000.2554.62475.23338.35843.32769.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17585249408294027265.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4094384938.2349039617.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.62475.23338.35843.32769.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf40b5b2a8c0300107ea5ce32bd83b97]
Custom data block1 (32 bit): [0xf40b5b2a]
Custom data block2 (16 bit): [0x8c03]
Custom data block3 (12 bit): [0x001]
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: [0xf40b] 0b1111010000001011
Milliseconds: [0x5b] 357 (deviation -2ms..2ms)
Seconds: [0x2a] 42
Minute of day: [0x038c] 908 (15:07)
Day of year: [0x010] 16 (Day=16, 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-16 15:07:42'357 (deviation -2ms..2ms)