Interpret a UUID
Back
Your input: 49a19634-b102-8311-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:49a19634-b102-8311-87ea-5ce32bd83b97
URI: uuid:49a19634-b102-8311-87ea-5ce32bd83b97
Microsoft GUID syntax: {49A19634-B102-8311-87EA-5CE32BD83B97}
C++ struct syntax: { 0x49a19634, 0xb102, 0x8311, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.97872650022609848005895426331102428055
As OID (Microsoft): 1.2.840.113556.1.8000.2554.18849.38452.45314.33553.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.5305686989071352593.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1235326516.2969731857.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.18849.38452.45314.33553.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x49a19634b10231107ea5ce32bd83b97]
Custom data block1 (32 bit): [0x49a19634]
Custom data block2 (16 bit): [0xb102]
Custom data block3 (12 bit): [0x311]
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: [0x49a1] 0b0100100110100001
Milliseconds: [0x96] 588 (deviation -2ms..2ms)
Seconds: [0x34] 52
Minute of day: [0x02b1] 689 (11:28)
Day of year: [0x113] 275 (Day=2, Month=10)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-10-02 11:28:52'588 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing