Interpret a UUID
Back
Your input: 95f97c09-1b05-850d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:95f97c09-1b05-850d-87ea-5ce32bd83b97
URI: uuid:95f97c09-1b05-850d-87ea-5ce32bd83b97
Microsoft GUID syntax: {95F97C09-1B05-850D-87EA-5CE32BD83B97}
C++ struct syntax: { 0x95f97c09, 0x1b05, 0x850d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.199350369029934720796300980461715864471
As OID (Microsoft): 1.2.840.113556.1.8000.2554.38393.31753.6917.34061.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.10806805159402112269.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2516155401.453346573.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.38393.31753.6917.34061.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x95f97c091b0550d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x95f97c09]
Custom data block2 (16 bit): [0x1b05]
Custom data block3 (12 bit): [0x50d]
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: [0x95f9] 0b1001010111111001
Milliseconds: [0x7c] 486 (deviation -2ms..2ms)
Seconds: [0x09] 9
Minute of day: [0x051b] 1307 (21:46)
Day of year: [0x0d5] 213 (Day=1, 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-01 21:46:09'486 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing