Travel fares · Ferry fares
Ferry fare monitoring: routes, seasons and vehicles
A ferry fare is rarely one number. It depends on the sailing, the season, the vehicle and its size, the cabin, and sometimes on whether the traveller is a resident. Monitor it as a matrix of standard configurations per route, collected from each operator's own public booking flow.
Pay per GB · No subscription · Prices in EUR, excl. VAT
- €2.00
- per GB on ARC Fast, excl. VAT
- −44%
- at 1 TB (€1.12 / GB)
- 185+
- countries, city targeting
- Never
- expires — no subscription
Written for
- Ferry comparison and booking sites
- Island tourism boards
- Ferry operators' pricing teams
- Maritime transport researchers
The short answer
- Ferries are mass transport. EU ports recorded 417.8 million passengers in 2024, up 6.2%; the busiest were Messina, Reggio di Calabria and Napoli (Eurostat).
- Price = sailing × vehicle × passengers × accommodation. Define a few standard configurations and collect those, not every combination.
- Resident and social fares are legitimate and large, for example Spain's 75% resident discount for the Canary and Balearic Islands, Ceuta and Melilla. Keep them out of the general-public series.
- Operators are often small. Collect slowly, from the operator's home market, and refresh seasonal timetables as soon as they are published.
The problem
What goes wrong without the right IPs
The vehicle moves the price more than the date
A car, a car with a roof box, a camper van and a motorbike are four different prices on the same sailing, and length and height bands matter. A 'ferry price' without the vehicle configuration cannot be compared.
Seasonal timetables arrive late and change
Summer sailings are often published months in advance, then adjusted. A monitor that only reads the current timetable misses new sailings, and keeps querying cancelled ones until it errors.
Resident fares look like price drops
Flows that offer a resident or discount option can return a discounted price if the option is pre-selected or remembered. Record the passenger type on every row, and exclude anything that is not a general-public adult fare from the main series.
One route, several operators
Busy crossings are often served by competing operators with different vessels, durations and fare rules. Each one needs its own collection and normalisation.
Small sites, small capacity
Regional operators run modest booking systems. Heavy parallel collection is noticeable, and it is unfair to their real customers. Low concurrency per operator and polite backoff are part of the job, not an extra.
What to collect
What you can collect
- Route, operator and vessel
- Fast craft and conventional ferries on one route are different products.
- Sailing date and time
- Peak sailings and night crossings are priced differently.
- Foot-passenger fare
- The reference price: one adult, general public.
- Vehicle type and size band
- Car, van, camper or motorbike, by the operator's length and height bands.
- Accommodation
- Deck seat, reclining seat, or cabin type on overnight routes.
- Fare type
- Standard, flexible or promotional, with change conditions.
- Passenger type flag
- General public vs resident or other social tariffs, kept separate.
- Availability
- Vehicle decks sell out before passenger capacity does in peak season.
- Market, currency and observation time
- International routes sell in several editions.
How it runs
How a collection run works
- 01
Define standard configurations
Pick three to five configurations that reflect real demand, for example foot passenger, two adults with a standard car, and a family with a car and a cabin. Every route is priced in the same configurations.
- 02
Build the sailing calendar
Read published schedules on the cheap rotating pool and refresh them weekly, and daily when a new season is published. This is the list of sailings you price.
- 03
Price each configuration with a sticky session
Run the public booking flow once per sailing date and configuration, holding one residential exit from route selection to the price summary. Stop before passenger details or payment.
- 04
Throttle per operator
Cap concurrency per operator to a handful of flows and back off on errors. A full sweep that takes a few hours is fine for prices that move daily, not by the minute.
- 05
Watch for season changes
Diff the sailing calendar on every run. New sailings, dropped sailings and changed times are signals in their own right, especially for tourism boards tracking island access.
Setup
Recommended setup
Ferry booking flows are short but stateful. Schedules are static. The split is the same as for air, at a fraction of the volume.
| Plan | Role | Session | Targeting | Price |
|---|---|---|---|---|
ARC Fast Rotating residential | Booking-flow pricing Residential exits in the operator's home market, held from route selection to the price summary. | Sticky, about 10 minutes per flow | Country | €2.00 / GB €1.12 at 1 TB (−44%) |
ARC Basic Rotating ISP | Schedules and fare-condition pages Timetables and conditions change slowly and do not vary by visitor. Cheapest per GB. | Rotating | Country | €0.75 / GB €0.59 at 1 TB (−21%) |
Prices are list prices in EUR, excl. VAT. Volume discounts apply automatically at checkout — full ladder on the pricing page.
Connect
One connection string per market
The country, city and sticky session are tokens in the username. Change the token, change the market; keep the session handle, keep the IP.
http://USERNAME_pool-arcfast_country-de_session-k3f9a1x2_sesstime-10:PASSWORD@proxy.arcproxies.io:8000Swap _country-de for any market you quote. The full grammar is on the residential proxies page.
Illustration
What forty ferry routes, twice a week costs
An illustration with round numbers — your pages, payloads and retry rate will differ. The arithmetic is the real price ladder.
Assumptions
- Routes
- 40
- Sailing dates ahead
- 120
- Configurations per sailing date
- 3
- Cadence
- twice a week (8.6 a month)
- Weight per pricing flow
- 300 KB
- Bandwidth per month
- ≈ 38 GB
On ARC Fast
€69.92per month, excl. VAT
38 GB bought in one purchase at €1.84 / GB (−8% volume rung, applied automatically).
The same 38 GB on ARC Basic: €28.50 at €0.75 / GB. Move down as soon as the cheaper pool holds up.
Most ferry flows return every sailing of a date at once, so the matrix counts dates, not individual sailings. Doubling the cadence in peak season doubles the figure.
Bandwidth never expires, so a bigger single purchase is only ever cheaper per GB. See the ladder.
In depth
Ferry fares, in depth
What drives a ferry fare
| Driver | Typical options | How to model it |
|---|---|---|
| Sailing | Peak and off-peak departures, day and night crossings | One row per sailing; keep the time |
| Season | Summer and holiday peaks, winter timetables | Price the same dates across seasons; tag the timetable version |
| Vehicle | None, car, van, camper, motorbike, trailer | Operator's length and height bands mapped to a few standard sizes |
| Passengers | Adults, children, infants | Fixed configurations, e.g. one adult, or two adults with a car |
| Accommodation | Deck, reclining seat, cabin types | Price a seat by default; add a cabin configuration on overnight routes |
| Passenger type | General public, resident, other social tariffs | General public only in the main series; anything else flagged |
Seasonality and the timetable
Ferry demand is heavily seasonal, and capacity follows the timetable rather than the other way round. That makes the publication of a new season's timetable, and its first prices, one of the most valuable observations of the year for comparison sites and tourism boards alike.
Collect the same sailing dates across the year, so a July crossing priced in January, March and June gives you a booking curve. Vehicle space on peak sailings often sells out before foot-passenger capacity, so record availability with the price.
Who uses ferry price data
- Ferry comparison sites need sailings, prices per configuration and availability across operators, refreshed often enough that a quoted fare is still bookable.
- Island tourism boards watch the cost of getting there: peak-season vehicle fares, capacity on key sailings and how both compare with last year. That is the access cost of the destination, alongside hotel rates.
- Operators' pricing teams track competitors on shared routes, and substitutes such as airline fares to the same island.
- Researchers need consistent, documented series: fixed configurations, timestamps and a stated method. Travel fare aggregation covers the shared setup across modes.
Collecting gently from small operators
Many ferry operators are small companies with booking systems sized for their customers, not for monitors. Keep a low concurrency cap per operator, back off on 429 and 5xx responses (handling 429 rate limits), cache schedules and conditions, and only price what your product needs.
Check each operator's terms and robots.txt, stay logged out, and stop before passenger details. Where an operator offers an agent or partner feed, it is usually the better source. See collecting travel data responsibly.
Works with anything that takes a proxy URL
Playwright
- Python requests / httpx
Crawlee
- changedetection.io
- Docker
FAQ
Questions
Something not covered? Write to contact@arcproxies.io.
Why are ferry prices so different for cars?
Vehicle deck space is a scarce, separately priced resource. Operators charge by vehicle type and by length and height bands, and peak-season vehicle space often sells out before passenger capacity does. Always store the vehicle configuration with the fare.
How far ahead should I monitor ferry fares?
Far enough to cover the published timetable, often several months, with denser collection close to peak dates. Pricing the same sailing dates repeatedly over time gives you a booking curve, which is more useful than a single snapshot.
Are resident ferry discounts legal in the EU?
EU sea-passenger rules prohibit discrimination based on nationality or on the carrier's place of establishment, but explicitly without prejudice to social tariffs. Resident discounts such as Spain's 75% subsidy for the Canary and Balearic Islands, Ceuta and Melilla exist on that basis. This is a summary, not legal advice.
Should I monitor foot-passenger or vehicle fares?
Both, as separate configurations. Foot-passenger fares are the clean reference price, while vehicle fares carry most of the revenue and most of the seasonal variation on many routes. Pick three to five standard configurations and price every route in all of them.
How much bandwidth does ferry fare monitoring use?
Not much. Forty routes, 120 sailing dates and three configurations priced twice a week comes to about 37 GB a month in our illustration. Bandwidth is billed per GB and never expires, which suits seasonal monitoring that is busy in spring and quiet in winter.
Sources & review
Last reviewed by the ARC Proxies team. Prices are read from the live catalog at build time.
- [1]Eurostat: Maritime passengers in EU up by 24.3 million in 2024
- [2]EUR-Lex (Official Journal of the European Union): Regulation (EU) No 1177/2010 concerning the rights of passengers when travelling by sea and inland waterway
- [3]Boletín Oficial del Estado: Real Decreto 949/2018, de 27 de julio (subvención al transporte de residentes en territorios no peninsulares)
Travel fares
More on travel fares
Get started
Buy a gigabyte and try it on your own targets.
No subscription, no sales call. Code WELCOME15 takes 15% off your first purchase, and whatever you do not use is still there next quarter.