Interpret a UUID
Back
Your input: 58a4430b-2001-8d10-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:58a4430b-2001-8d10-87ea-5ce32bd83b97
URI: uuid:58a4430b-2001-8d10-87ea-5ce32bd83b97
Microsoft GUID syntax: {58A4430B-2001-8D10-87EA-5CE32BD83B97}
C++ struct syntax: { 0x58a4430b, 0x2001, 0x8d10, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.117824960116730936264158529795611179927
As OID (Microsoft): 1.2.840.113556.1.8000.2554.22692.17163.8193.36112.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.6387303886578879760.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1487160075.536972560.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.22692.17163.8193.36112.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x58a4430b2001d1007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x58a4430b]
Custom data block2 (16 bit): [0x2001]
Custom data block3 (12 bit): [0xd10]
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: [0x58a4] 0b0101100010100100
Milliseconds: [0x43] 262 (deviation -2ms..2ms)
Seconds: [0x0b] 11
Minute of day: [0x0120] 288 (04:47)
Day of year: [0x10d] 269 (Day=26, 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-26 04:47:11'262 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing