Finding an entry — search and the summary view

Modified on Tue, 28 Jul at 11:39 PM

Two ways back into a logbook that has grown: Search when you are looking for something specific, Summary when you want the shape of a season. Both are in the left sidebar and both work without a connection.

Search

Type anything — a port, a name, a date — and KnotWise searches across passages, log entries, maintenance and inventory at once. Recent searches are kept, so a query you use often is one tap away.

Narrowing it down with operators

Where plain text returns too much, an operator makes the search precise:

OperatorFinds
port:Departure or arrival port
country:Country
crew:Watch officer
bft:Beaufort force, exact value
cat:Maintenance category
date:Date, also as a prefix — a year or a month is enough

Operators combine. port:Hamburg bft:7 finds the legs to or from Hamburg where force 7 was logged — the sort of question a paper logbook cannot answer at all.

Summary

Summary aggregates your entries over a period you choose: yesterday, the last 7, 30 or 90 days, a whole season, or a single passage. It shows distance sailed, average speed over ground, average and maximum wind, engine hours and fuel used — plus a wind rose showing which directions you actually had.

Two uses beyond curiosity: the engine hours and fuel figures are what an insurer or a buyer asks about, and a season comparison shows quickly whether the log has gaps.

Both read your entries and nothing else. A field left empty appears nowhere — an average wind speed is calculated from the entries that carry one. That is the practical argument for filling in the fields you care about consistently rather than completely.

Both work on every plan and without a connection. Getting the numbers out of the app: Exporting your logbook.

Last updated: 28 July 2026

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article