Interpret a UUID
Back
Your input: 0461b902-cf03-8610-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:0461b902-cf03-8610-87ea-5ce32bd83b97
URI: uuid:0461b902-cf03-8610-87ea-5ce32bd83b97
Microsoft GUID syntax: {0461B902-CF03-8610-87EA-5CE32BD83B97}
C++ struct syntax: { 0x0461b902, 0xcf03, 0x8610, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.5824317246718199271667417109430287255
As OID (Microsoft): 1.2.840.113556.1.8000.2554.1121.47362.52995.34320.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.315736870606833168.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.73513218.3473114640.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.1121.47362.52995.34320.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x0461b902cf0361007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x0461b902]
Custom data block2 (16 bit): [0xcf03]
Custom data block3 (12 bit): [0x610]
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: [0x0461] 0b0000010001100001
Milliseconds: [0xb9] 725 (deviation -2ms..2ms)
Seconds: [0x02] 2
Minute of day: [0x03cf] 975 (16:14)
Day of year: [0x106] 262 (Day=19, 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-19 16:14:02'725 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing