Interpret a UUID
Back
Your input: b924f800-a103-8f00-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:b924f800-a103-8f00-87ea-5ce32bd83b97
URI: uuid:b924f800-a103-8f00-87ea-5ce32bd83b97
Microsoft GUID syntax: {B924F800-A103-8F00-87EA-5CE32BD83B97}
C++ struct syntax: { 0xb924f800, 0xa103, 0x8f00, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.246099131994529784562992735719947516823
As OID (Microsoft): 1.2.840.113556.1.8000.2554.47396.63488.41219.36608.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.13341060677763305216.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3106207744.2701364992.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.47396.63488.41219.36608.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xb924f800a103f0007ea5ce32bd83b97]
Custom data block1 (32 bit): [0xb924f800]
Custom data block2 (16 bit): [0xa103]
Custom data block3 (12 bit): [0xf00]
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: [0xb924] 0b1011100100100100
Milliseconds: [0xf8] 972 (deviation -2ms..2ms)
Seconds: [0x00] 0
Minute of day: [0x03a1] 929 (15:28)
Day of year: [0x00f] 15 (Day=15, 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-15 15:28:00'972 (deviation -2ms..2ms)