The values displayed should not be interpreted as exact times for a single trip, but rather as a comparable basis for assessing local mobility quality. They may therefore differ from individually measured times.

This is because mobi.mapr does not show pure travel time, but rather a systematically calculated mobility time. This takes into account various aspects of everyday mobility and thus goes beyond a traditional route calculation.

For example: According to navigation, the trip to the supermarket might take three minutes by car, six minutes by bike, or nine minutes on foot. In everyday life, however, additional time is required—such as for parking or locking up the bike—which mobi.mapr systematically factors in.

At the same time, typical behavioral patterns are also taken into account: For very short distances, people often choose to walk, even if the bike would theoretically be faster—for example, because they first have to fetch it from the basement and then put it away again, which takes additional time.

Furthermore, the algorithm considers not just individual destinations but multiple feasible options, which are weighted against one another—after all, people don’t always want to go to the same supermarket.

Mobility time is therefore not an exact route specification, but a realistic, comparable time estimate for everyday mobility.