Interpret a UUID
Back
Your input: b24f1312-c802-850e-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b24f1312-c802-850e-87ea-5ce32bd83b97
URI: uuid:b24f1312-c802-850e-87ea-5ce32bd83b97
Microsoft GUID syntax: {B24F1312-C802-850E-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb24f1312, 0xc802, 0x850e, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.237013161555328719556726321789961517975
As OID (Microsoft): 1.2.840.113556.1.8000.2554.45647.4882.51202.34062.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.12848509233297261838.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2991526674.3355608334.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.45647.4882.51202.34062.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb24f1312c80250e07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb24f1312]
Custom data block2 (16 bit): [0xc802]
Custom data block3 (12 bit): [0x50e]
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: [0xb24f] 0b1011001001001111
Milliseconds: [0x13] 74 (deviation -2ms..2ms)
Seconds: [0x12] 18
Minute of day: [0x02c8] 712 (11:51)
Day of year: [0x0e5] 229 (Day=17, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-17 11:51:18'074 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing