Interpret a UUID
Back
Your input: 9c878a22-7505-820b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9c878a22-7505-820b-87ea-5ce32bd83b97
URI: uuid:9c878a22-7505-820b-87ea-5ce32bd83b97
Microsoft GUID syntax: {9C878A22-7505-820B-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9c878a22, 0x7505, 0x820b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.208063329120848312216897647831139498903
As OID (Microsoft): 1.2.840.113556.1.8000.2554.40071.35362.29957.33291.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11279135672369512971.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2626128418.1963295243.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.40071.35362.29957.33291.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9c878a22750520b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9c878a22]
Custom data block2 (16 bit): [0x7505]
Custom data block3 (12 bit): [0x20b]
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: [0x9c87] 0b1001110010000111
Milliseconds: [0x8a] 541 (deviation -2ms..2ms)
Seconds: [0x22] 34
Minute of day: [0x0575] 1397 (23:16)
Day of year: [0x0b2] 178 (Day=27, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-27 23:16:34'541 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing