Statistics — how the values are calculated

Number of logbook entries on the day in question or during the whole trip.

Graphical representation of how the speed developed over the day or over the whole trip.

Track based — source: position / time. The light blue line shows the speed calculated from the distances between the entries and the time stored in them.

Log based — source: speed (SOG). The dark blue line shows the speed stored in the logbook entry — that is, the speed measured via GPS when the entry was created or adjusted manually later on.

Source: speed (SOG). The average speed based on the entries in the logbook, i.e. from the dark blue line.

Source: position / time. The average speed calculated from the GPS track, i.e. from the light blue line.

Source: speed (SOG). The maximum speed based on the entries in the logbook (dark blue line).

Source: position / time. The maximum speed calculated from the GPS track (light blue line).

Source: air pressure. The air pressure trend from the logbook entries. Reliable and highly accurate on devices with a barometer, otherwise taken from the internet.

Graphical representation of what is described under point 10.

Graphical representation of what is described under points 11 and 12.

Source: position. This shows the distance covered. It is calculated from the distances between the individual entries and positions in the logbook.

Split between sail / engine — source: status. The app distinguishes in which status (engine, sail, at anchor, moored, motor sailing) you covered the distance. Motor sailing counts as travelling under engine. Normally no distance should be covered with the status at anchor or moored — if that does happen, it is shown in red as a warning from about 0.3 nautical miles. This is why it is essential to always keep the status up to date while under way. If you forgot, it can also be updated afterwards for several entries at once.

Continuous log — source: log. For the daily statistics: if there is at least one entry with a log value greater than 0 on that day plus an entry on an earlier day, the last value of the day is shown as the total log reading and the difference to the last older entry as the distance covered. If there is no earlier day but at least two entries on the same day, the difference within the day is used. Otherwise nothing is shown. For the whole trip: from two entries with a log value greater than 0 onwards, the last value is shown as the total log reading and the difference to the first entry as the distance.

Source: time. The elapsed time based on the times of the individual entries. Over several days the first day starts with the first entry and the last day ends with the last entry (e.g. 08:00 to 24:00 = 16 h); days in between always count 24 h. If there is only one day, it runs from the first to the last entry. In addition the app distinguishes in which status (engine, sail, etc.) the time elapsed.

Source: status / time. Same as point 11, but for the statuses at anchor and moored.

Source: engine running hours. Running hours can be entered for up to three engines. This value may differ from the engine time derived from the status, because it can be overwritten manually and also covers running times without travel — for example when the engine charges the batteries at anchor. There are two calculation methods in the settings.

Difference (called “log” up to version 2.34): you copy the value from the ship's engine hour meter and the difference is displayed. Example: day 1 with 1,024.5 h, day 2 with 1,028.5 h results in four hours for day 2. If there is only one entry on a day, an earlier day is searched for comparison; if none is found, nothing is shown. If there are several entries on the day, the difference between the first and the last one counts. If a newer value is smaller than an older one, an error message appears. The same calculation applies to the whole trip.

Add up: intended for entering individual running times — e.g. 1 h in the morning and 1.5 h in the afternoon results in 2.5 h. All values are added up per engine. Since running hours have always been pre-filled using the other principle from version 2.45 onwards, this calculation method is only relevant for old logbooks.