Interpret a UUID
Back
Your input: b5c2ce19-ee04-8109-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b5c2ce19-ee04-8109-87ea-5ce32bd83b97
URI: uuid:b5c2ce19-ee04-8109-87ea-5ce32bd83b97
Microsoft GUID syntax: {B5C2CE19-EE04-8109-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb5c2ce19, 0xee04, 0x8109, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.241601753058370822058089081362223479703
As OID (Microsoft): 1.2.840.113556.1.8000.2554.46530.52761.60932.33033.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13097257277109600521.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3049442841.3993272585.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.46530.52761.60932.33033.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb5c2ce19ee0410907ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb5c2ce19]
Custom data block2 (16 bit): [0xee04]
Custom data block3 (12 bit): [0x109]
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: [0xb5c2] 0b1011010111000010
Milliseconds: [0xce] 807 (deviation -2ms..2ms)
Seconds: [0x19] 25
Minute of day: [0x04ee] 1262 (21:01)
Day of year: [0x091] 145 (Day=25, Month=5)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-05-25 21:01:25'807 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing