@Guzzist Thank you for your suggestion, will add it to the suggestion list.

From a design perspective I have to say though that I really dislike how steep and complex the basecamp data looks. While I will directly agree that it'd be important for people who like such complexity to be able to view this, I will most certainly try to improve the visual presentation of this. Especially in an app it's important to view things as efficiently as possible. Perhaps a solution would be to be able to download or open a data-pdf for a more in depth look.

Your general point: lunch pauses should not be included in total duraction and averages, is of course correct.

@Guzzist Thank you for clarifying that, Your comment interested me so I looked it up a little more on wikipedia and found this:

". While driving at higher speeds is not punishable, the increased risk induced by higher speeds (erhöhte Betriebsgefahr) may result in partial liability for damages. Moreover, the law forbids travel at speeds that would extend the vehicle's minimum halting distance beyond the driver's line of sight (Sicherheitsabstand).[16] On all German roads, there are speed limits for trucks, buses, cars towing trailers, and small motorised vehicles (Mopeds, etc.)."

Someone also told me that German insurers start holding you liable at speeds over 160 km/h. I'm not sure how accurate that is. Regardless, I might think twice now about going over 200.