Interpret a UUID
Back
Your input: f4bf7039-9c04-8308-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:f4bf7039-9c04-8308-87ea-5ce32bd83b97
URI: uuid:f4bf7039-9c04-8308-87ea-5ce32bd83b97
Microsoft GUID syntax: {F4BF7039-9C04-8308-87EA-5CE32BD83B97}
C++ struct syntax: { 0xf4bf7039, 0x9c04, 0x8308, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.325325635865665613388518212652831882135
As OID (Microsoft): 1.2.840.113556.1.8000.2554.62655.28729.39940.33544.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.17635938058539139848.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.4106186809.2617541384.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.62655.28729.39940.33544.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xf4bf70399c0430807ea5ce32bd83b97]
Custom data block1 (32 bit): [0xf4bf7039]
Custom data block2 (16 bit): [0x9c04]
Custom data block3 (12 bit): [0x308]
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: [0xf4bf] 0b1111010010111111
Milliseconds: [0x70] 439 (deviation -2ms..2ms)
Seconds: [0x39] 57
Minute of day: [0x049c] 1180 (19:39)
Day of year: [0x083] 131 (Day=11, Month=5)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-05-11 19:39:57'439 (deviation -2ms..2ms)