The Adriatic fishing map fishing layers are live for Trieste-Ancona, the Slovenian coast, Istria, Kvarner and Dalmatia. Outside that box the base map opens without fishing layers. Coverage is Adriatic-only.
Updated 2026. Status verified 18 September 2026.
Which Adriatic coasts does AlgoCatch cover?
Five coasts: Trieste-Ancona, the Slovenian coast, Istria, Kvarner and Dalmatia. That is the whole coverage box; AlgoCatch does not add coasts on request and is not a worldwide fishing chart. The base map opens elsewhere without fishing layers.
AlgoCatch coverage is that list and nothing else. The in-app outline traces the same five names. If a hotel sits on one of those coasts, the fishing layers are in play. If it does not, you get the base map only. We do not add a coast because someone wrote in.
This section is for any visitor checking their base before they sign up. How you use it: read the five names, then look at the dated table in the next section for what is live versus partial. When it applies: as of 18 September 2026. Additions happen inside the box, never by inventing a sixth coast.
The box is not a paraphrase and not a basin slogan. It is not "the Croatian side" and not an open list. It is not a worldwide fishing chart. The camera can pan further. Fishing layers do not. Write the five names down before you book the apartment if the map is why you came.
What is live on each coast?
Depth contours and Folk-5 seabed are live across the whole box. Habitat and scoring tools are complete on four coasts; on the remaining strip some habitat and mode layers are still partial.
The table is the status, not a brochure. Depth and seabed sit on every row because EMODnet Bathymetry and EMODnet Geology cover the Adriatic uniformly. Habitat species, technique modes and the scoring columns are the cells that can be partial. Guides are a count of English town pages, not a layer.
This table is for the visitor on the western sandy strip who needs honesty before paying, and for the boat week that needs to know scoring tools run on the other four coasts. How you read it: find your row. A live cell means that layer runs today. A partial cell means some of that layer is still incomplete. Not yet would mean it is off; no row uses that today.
When: verified 18 September 2026. We refresh the caption when a partial cell flips to live.
| Coast | Depth | Folk-5 | Habitat species | Technique modes | Spot Finder | Route suggestions | Guides |
|---|---|---|---|---|---|---|---|
| Trieste-Ancona | live | live | partial | partial | partial | partial | 6 |
| Slovenian coast | live | live | live | live | live | live | 3 |
| Istria | live | live | live | live | live | live | 5 |
| Kvarner | live | live | live | live | live | live | 3 |
| Dalmatia | live | live | live | live | live | live | 9 |
The honest phrase is partial on Trieste-Ancona.
What happens outside the coverage box?
The base map opens without depth tint, Folk-5 seabed or habitat layers, and a notice says fishing data is live in the Adriatic. Scoring tools refuse to run; the Go to coverage button jumps to covered water.
The in-app notice reads: "AlgoCatch fishing data is live in the Adriatic Sea". That is expected, not a crash. Spot Finder, the structure-edge finder and route tools refuse to run by design once you leave the box. Go to coverage jumps the camera back to covered water. An interest banner may ask where you fish so the team knows what to build next. It does not promise a new sea.
This is for the visitor who opens the map from home and pans, or who types a place that sits outside the outline. How you act: read the notice, tap Go to coverage, or search a covered harbour. When it happens: immediately on leaving the box. When it stops: as soon as the camera is back on covered water.
The base map opens without fishing layers on purpose. We would rather show you empty water than invent a score for a coast the model does not run. That refusal is the product working, not the tiles failing.
How many place guides does each coast have?
Guide counts are uneven. The Guides column in the table is the English town-page count from the location hub, verified 18 September 2026. A coast with fewer guides still has map layers; the guides teach places, the layers cover the whole box.
Readers confuse two things. A thin guide list is not a dead map. Layers cover the whole box regardless of how many town pages exist. The largest count in the table is nine. The smallest is three. Both rows still show live depth and seabed.
This section is for the boat week that finds few town pages and assumes the map is empty. How you use it: open the map layers even where the guide list is short. The location hub, under Fishing location guides, lists what exists. When: the counts above are dated 18 September 2026. They change when a new English town page ships, not when a layer ships.
Do not wait for a town page before you tap the water you will actually fish. A missing guide is a missing lesson, not a missing layer.
Why is coverage limited to the Adriatic?
Because the habitat model is built on Adriatic seabed classes, uniform depth data and local years on these coasts. Additions happen inside the box, like completing the western sandy strip, never by adding another sea. Depth data does not make a coast covered.
Three ingredients have to sit together: the seabed classes the model was built on, the depth grid, and sessions on the water. Uniform depth exists more widely than our box. That is not enough. We do not call a coast covered because a depth tile exists. We call it covered when the fishing layers run for the species and techniques the table names.
Who this answers: anyone asking us to jump the box. How additions work: we finish partial cells inside the outline. Completing the remaining strip is the current inside-the-box job. When: only inside the box. The rule is additions inside the box, never another sea. The AlgoCatch founders page is where those local years are named.
A visitor who saw a depth number on a public chart and asked us to "just switch the layer on" is asking for a score we do not compute there. The model is not a tint. It is a habitat read that needs the three ingredients at once. This is not an open expansion promise. Never another sea.
Does coverage change with your plan or account?
No. Free and paid see the same coverage box; a pass unlocks species and limits, not coasts. Some accounts have a smaller allowed rectangle and see "Your location is outside your allowed map area"; pan inside it or ask support.
There is same coverage on Free and VIP. Paying does not add a coast. A pass changes what you can unlock inside the box, not the outline of the box. If you bought a pass hoping it would light up a sixth coast, that is the wrong reason to pay.
A separate case is the account rectangle. Some accounts are limited to a smaller allowed map area. The message is: "Your location is outside your allowed map area". That is not the coverage box failing. Pan back inside the rectangle, or write to support if the rectangle is wrong for your trip.
Who this is for: the buyer who thinks a pass widens the map, and the signed-in user who hit the rectangle message. How: check the table for your coast, then decide a pass only for species and limits. When: always. The box does not move with the plan.
If your coast row is live, open the free map and tap the water you will fish. If a cell is partial, treat that layer as incomplete and use the layers that are live. If you have panned away, tap Go to coverage. Do not buy a pass to widen the outline. Species and limits change with a pass; coasts do not. Details: AlgoCatch free vs VIP plans.
FAQs
Which areas does AlgoCatch cover?
Five named coasts inside one coverage box, stated on this page and in the app outline. Fishing layers are live there. The base map can open elsewhere without those layers. AlgoCatch does not add coasts on request. It is not a worldwide fishing chart. Read the dated table for live versus partial cells on each row.
Does AlgoCatch work in Dalmatia?
Yes. Depth, seabed, species habitat layers and scoring tools are live on that row in the table, the same as the two neighbouring Croatian rows. Place guides there are growing; a thinner guide list does not turn the layers off.
Does AlgoCatch cover Italy?
The Adriatic shore inside the coverage box is included. Depth and seabed are live along that strip; some habitat and technique-mode layers are still partial, as marked in the status table. This page does not claim the rest of that country.
Does AlgoCatch cover the whole Adriatic?
No. Fishing layers are live on the five coasts in the coverage box, not on every shore of the basin. The base map may still pan. Scoring tools refuse to run outside the outline. Additions happen inside the box. We do not sell a whole-basin claim.
Why does the map show no fishing data where I am?
You are outside the coverage box, or inside an account rectangle that is smaller than the box. The notice says fishing data is live in the Adriatic. Tap Go to coverage, or pan back inside your allowed map area. If the rectangle is wrong, write to support. Empty layers outside the box are by design.
Is AlgoCatch a worldwide fishing map?
No. It is not a worldwide fishing chart. Fishing layers are live only inside the coverage box on this page. The base map can open in other places so you can see land and water, but depth tint, seabed and habitat stay off. Do not treat a panned camera as coverage.
By Gregor Romavh, co-founder of AlgoCatch, 30+ years of Adriatic shore and boat fishing from the Slovenian coast to Dalmatia.