Interpret a UUID
Back
Your input: 95f8aa2e-b502-8310-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:95f8aa2e-b502-8310-87ea-5ce32bd83b97
URI: uuid:95f8aa2e-b502-8310-87ea-5ce32bd83b97
Microsoft GUID syntax: {95F8AA2E-B502-8310-87EA-5CE32BD83B97}
C++ struct syntax: { 0x95f8aa2e, 0xb502, 0x8310, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.199346112703017022318928005678002355095
As OID (Microsoft): 1.2.840.113556.1.8000.2554.38392.43566.46338.33552.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.10806574423457563408.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2516101678.3036840720.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.38392.43566.46338.33552.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x95f8aa2eb50231007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x95f8aa2e]
Custom data block2 (16 bit): [0xb502]
Custom data block3 (12 bit): [0x310]
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: [0x95f8] 0b1001010111111000
Milliseconds: [0xaa] 666 (deviation -2ms..2ms)
Seconds: [0x2e] 46
Minute of day: [0x02b5] 693 (11:32)
Day of year: [0x103] 259 (Day=16, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-16 11:32:46'666 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing