Interpret a UUID
Back
Your input: a3fb4f30-2202-8c0a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:a3fb4f30-2202-8c0a-87ea-5ce32bd83b97
URI: uuid:a3fb4f30-2202-8c0a-87ea-5ce32bd83b97
Microsoft GUID syntax: {A3FB4F30-2202-8C0A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xa3fb4f30, 0x2202, 0x8c0a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.217969035948269587695867148280142510999
As OID (Microsoft): 1.2.840.113556.1.8000.2554.41979.20272.8706.35850.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.11816125115484245002.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2751156016.570592266.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.41979.20272.8706.35850.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xa3fb4f302202c0a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xa3fb4f30]
Custom data block2 (16 bit): [0x2202]
Custom data block3 (12 bit): [0xc0a]
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: [0xa3fb] 0b1010001111111011
Milliseconds: [0x4f] 309 (deviation -2ms..2ms)
Seconds: [0x30] 48
Minute of day: [0x0222] 546 (09:05)
Day of year: [0x0ac] 172 (Day=21, 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-21 09:05:48'309 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing