Interprete a UUID
Back
Your input: 87f30d31-d503-8815-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:87f30d31-d503-8815-87e9-5ce32bd83b97
URI: uuid:87f30d31-d503-8815-87e9-5ce32bd83b97
Microsoft GUID syntax: {87F30D31-D503-8815-87E9-5CE32BD83B97}
C++ struct syntax: { 0x87f30d31, 0xd503, 0x8815, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.180707775187016993134837017484776192919
As OID (Microsoft): 1.2.840.113556.1.8000.2554.34803.3377.54531.34837.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.9796188122139297813.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2280852785.3573778453.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.34803.3377.54531.34837.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x87f30d31d50381507e95ce32bd83b97]
Custom data block1 (32 bit): [0x87f30d31]
Custom data block2 (16 bit): [0xd503]
Custom data block3 (12 bit): [0x815]
Custom data block4 (14 bit): [0x07e9]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x87f3] 0b1000011111110011
Milliseconds: [0x0d] 51 (deviation -2ms..2ms)
Seconds: [0x31] 49
Minute of day: [0x03d5] 981 (16:20)
Day of year: [0x158] 344 (Day=10, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-12-10 16:20:49'051 (deviation -2ms..2ms)