Interpret a UUID
Back
Your input: 9497bd12-d301-8005-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:9497bd12-d301-8005-87ea-5ce32bd83b97
URI: uuid:9497bd12-d301-8005-87ea-5ce32bd83b97
Microsoft GUID syntax: {9497BD12-D301-8005-87EA-5CE32BD83B97}
C++ struct syntax: { 0x9497bd12, 0xd301, 0x8005, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.197513615068631474147200446865159502743
As OID (Microsoft): 1.2.840.113556.1.8000.2554.38039.48402.54017.32773.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.10707234527643795461.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.2492972306.3540090885.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.38039.48402.54017.32773.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x9497bd12d30100507ea5ce32bd83b97]
Custom data block1 (32 bit): [0x9497bd12]
Custom data block2 (16 bit): [0xd301]
Custom data block3 (12 bit): [0x005]
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: [0x9497] 0b1001010010010111
Milliseconds: [0xbd] 740 (deviation -2ms..2ms)
Seconds: [0x12] 18
Minute of day: [0x01d3] 467 (07:46)
Day of year: [0x050] 80 (Day=21, Month=3)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-03-21 07:46:18'740 (deviation -2ms..2ms)