Interpret a UUID
Back
Your input: 041cb430-aa00-8513-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:041cb430-aa00-8513-87ea-5ce32bd83b97
URI: uuid:041cb430-aa00-8513-87ea-5ce32bd83b97
Microsoft GUID syntax: {041CB430-AA00-8513-87EA-5CE32BD83B97}
C++ struct syntax: { 0x041cb430, 0xaa00, 0x8513, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.5465950984472176755231360350621809559
As OID (Microsoft): 1.2.840.113556.1.8000.2554.1052.46128.43520.34067.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.296309796603200787.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.68990000.2852160787.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.1052.46128.43520.34067.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x041cb430aa0051307ea5ce32bd83b97]
Custom data block1 (32 bit): [0x041cb430]
Custom data block2 (16 bit): [0xaa00]
Custom data block3 (12 bit): [0x513]
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: [0x041c] 0b0000010000011100
Milliseconds: [0xb4] 705 (deviation -2ms..2ms)
Seconds: [0x30] 48
Minute of day: [0x00aa] 170 (02:49)
Day of year: [0x135] 309 (Day=5, Month=11)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-11-05 02:49:48'705 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing