Damn it! 
Doing the operations was my first idea... I managed to force pywallet to output something in hex, which I beleived, were the numbers:
33 + caea7cc3f8b198101e0f7ffb0eeb2e8c85ce9e72cc628990f30f41183aa6eba58761c239d03ded / 019385 (all in hex)
Doing these operations in gcalctool I ended up with this solution: 80BBC798A19A21A8BCEAA022375B1B73C73EF466CBE5B48D1DB1C195B26CC4603DDC2F897C
However, when this was imported into my wallet.dat, I didn't get the bitcoins (bitcoin was restarted with -rescan). What did I screw up?
Doing the operations was my first idea... I managed to force pywallet to output something in hex, which I beleived, were the numbers:
33 + caea7cc3f8b198101e0f7ffb0eeb2e8c85ce9e72cc628990f30f41183aa6eba58761c239d03ded / 019385 (all in hex)
Doing these operations in gcalctool I ended up with this solution: 80BBC798A19A21A8BCEAA022375B1B73C73EF466CBE5B48D1DB1C195B26CC4603DDC2F897C
However, when this was imported into my wallet.dat, I didn't get the bitcoins (bitcoin was restarted with -rescan). What did I screw up?
Ouch, bummer man.
Dani, a private key begins with a 5. That is quite different from a privkey.
A Wallet Import Format key does, but what he posted does indeed contain the hex private key, as Ean explains.