Port of Antwerp-Bruges Scraper for Two Merged Ports

One name, two ports, eighty kilometres apart, handling different cargo. Merge them in your data and every capacity figure describes a place that does not exist.

Plans from €169 a month · Free project assessment · Reply within 1 business day

CSV · Excel · JSON · XML · FTP · SFTP · Amazon S3 · Google Cloud

portofantwerpbruges.com
Port of Antwerp-Bruges Scraper for Two Merged Ports
portofantwerpbruges.comwhat you get
Typical fields for logistics sites
carrierorigindestinationservice_typepricetransit_days
Delivery

API, JSON feed or CSV, XLSX and JSON files

Schedule

One-time, monthly, weekly, daily or 3 times a day

Managed port data, run end to end by us

  1. You send

    Port of Antwerp-Bruges pages, filters, fields and a schedule

  2. We run the scrapers

    Built, monitored and repaired by our team

  3. You receive the data

    API, JSON feed or CSV, XLSX and JSON files

ScrapeIt runs the collection as a managed service. You name the sites, cargo types or terminals; we build the pipeline with site mandatory on every row, specialism vocabulary preserved and connections as a network, and hand back CSV, JSON, Excel or a push into your warehouse.

Published infrastructure data changes slowly, so periodic collection with change records fits better than a continuous feed and is what we quote.

We collect only publicly available data - everything a visitor can see on Port of Antwerp-Bruges - and we collect it legally, pacing requests as part of the service. This is a public authority's publication about infrastructure and contains no commercial or personal data.

Port of Antwerp-Bruges fields in every export

Records carry the site - Antwerp or Zeebrugge - alongside terminal name, operator, cargo specialism, location detail and the services described.

Site is mandatory and never inferred from context. The two locations have different depths, different hinterland connections and different cargo mixes, and an aggregate across them is a number for nowhere.

Cargo specialism is kept in the source's own vocabulary, which distinguishes containers, liquid bulk, chemicals, breakbulk, ro-ro and vehicles. Chemicals in particular are a distinct category here rather than a subset of liquid bulk, and flattening them loses what makes Antwerp what it is.

Hinterland connections are collected as rows by mode, as on any port source, because cargo leaving the quay is the question a supply chain model actually asks.

Every row carries the collection timestamp and the source address.

Port of Antwerp-Bruges fields in every export
Chemical cluster, ro-ro capacity and limits

Chemical cluster, ro-ro capacity and limits

Chemical cluster mapping is the distinctive output: which terminals handle which product groups, how they connect by pipeline, and what storage exists. For chemicals logistics it is a rare structured view of an industry that is otherwise opaque.

Ro-ro and vehicle handling capacity at the coastal site answers a question that container-centric port data cannot, and it matters to automotive supply chains in particular.

Comparative analysis between the two sites is only possible because they are recorded separately, and it is often the most interesting output - how a merged authority balances investment between two locations with different futures.

Limits: published information, not operations. No berth occupancy, no shipper volumes, no commercial terms. Promotional capacity claims are labelled as claims rather than folded in as measurements.

A merged authority over two distinct ports

Source
portofantwerpbruges.com
Category
logistics sites
Delivery
API, JSON feed, CSV, XLSX
Plans
From €169 a month
Get a quote

Port of Antwerp-Bruges is the authority formed by the merger of the ports of Antwerp and Zeebrugge. It is one organisation publishing under one name, and it operates two physically separate ports with substantially different profiles.

Antwerp is a deep inland port on the Scheldt, dominant in containers and the largest integrated chemical cluster in Europe. Zeebrugge is a coastal port strong in roll-on roll-off traffic, vehicles and liquefied natural gas. They are eighty kilometres apart and they do different things.

A dataset that takes the merged brand at face value and records a single port produces figures that describe neither location. Site has to be a field from the first row, and it is the most common error made with this source since the merger.

Port sections respond directly with substantial content. Everything a visitor sees there can be collected: site, terminal name, operator, cargo specialism, location detail, the services described and hinterland connections by mode.

25Developers
500+Customers
1.5BPages extracted
15,000+Hours saved for our clients

Port of Antwerp-Bruges scraping plans and pricing

Airplane

€199one-time

Setup fee included

100,000
One-time
Up to 5 days
7 days

Helicopter

€169/ mo

Setup fee €499

250,000
Monthly
Up to 5 days
14 days

Glasses

€229/ mo

Setup fee €499

1,000,000
Weekly
Up to 5 days
30 days

Microscope popular

€349/ mo

Setup fee €499

2,000,000
Daily
Same day
60 days

DNA

€549/ mo

Setup fee €799

3,000,000
3 times daily
Same day
90 days

Delivery: CSV, JSON or XLSX files, our API or a JSON feed. MCP server on request.

Full plan details

Why a merger is a data modelling problem

Corporate mergers create quiet data errors, because the brand consolidates faster than the physical reality it describes.

Here the two ports remain two ports. Their depths differ, so the vessels that can call differ. Their hinterland connections differ. Their cargo mixes barely overlap. Any analysis of capacity, congestion or routing that treats them as one facility will be wrong in ways that look plausible, because the merged figure sits between two real numbers and resembles both.

The second reason this source matters is the chemical cluster. Antwerp's chemical industry is the largest integrated cluster in Europe, and the port publishes terminal and pipeline detail about it that is hard to assemble elsewhere. For anyone in chemicals logistics that detail is the reason to come here at all.

The third is ro-ro and vehicles at Zeebrugge, a specialism with completely different infrastructure requirements from containers and one that container-focused datasets routinely ignore.

The fourth is the same limit as any port authority: this is published infrastructure and commercial information, not operational data, and we say what it is not as clearly as what it is.

Who builds and keeps your port feed

ScrapeIt is a managed extraction company, not a tool you have to learn. Our team builds the pipeline, keeps the two sites separated as the merged authority reorganises its publications, and repairs the collector before your model starts averaging two ports.

You see a sample first, in your format, over the cargo types you actually move, with site on every row so you can confirm nothing has been merged that should not be.

FAQ

Still unsure? Write to info@scrapeit.io

Is this one port or two?

One authority, two physical ports eighty kilometres apart with different depths, different hinterland links and barely overlapping cargo mixes. Site is a mandatory field, because a merged figure sits between two real numbers and resembles both while describing neither.

Why is chemicals a separate category?

Because Antwerp's chemical cluster is the largest integrated one in Europe and the port publishes terminal and pipeline detail about it. Folding chemicals into liquid bulk loses precisely what makes this source worth using for that industry.

What is at the coastal site?

Roll-on roll-off traffic, vehicles and liquefied natural gas primarily - specialisms with completely different infrastructure requirements from containers, and ones that container-focused port datasets routinely ignore.

Can I compare the two sites?

Yes, and only because they are recorded separately. It is often the most interesting output: how a merged authority balances investment between two locations with quite different futures.

Does this include actual throughput?

Only what the authority publishes. Berth occupancy, shipper volumes and commercial terms are not here. Capacity claims in promotional material are labelled as claims rather than presented as measurements.

How it works

  1. 1

    Make a request

    You share your needs, expectations, and desired timeframe. We'll suggest the best solution based on your request and budget.

  2. 2

    We configure the crawlers

    Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.

  3. 3

    Collect and deliver

    Once you approve the sample, we launch the project and start full data collection. We gather, filter, and structure the data for easy use, delivering it on time in your preferred format.

  4. 4

    Maintain and support

    Our team manages ongoing processes, monitors website changes, and supports all data extraction cycles. We can also help integrate data into your systems or create dashboards to simplify analysis.

Request a quote

Tell us which sites, which fields and how often. A couple of lines is enough to start.

  • We reply within 1 business day
  • A sample dataset before the full run
  • We sign an NDA on request
  • Delivery by API, JSON feed or files
Which sites, which fields, how often. A couple of lines is enough.

This form is protected by Google reCAPTCHA, which loads when you start filling it in. If you prefer not to use it, email us at info@scrapeit.io. Privacy & Cookie Policy

We reply within 1 business day. No obligation.

Port of Antwerp-Bruges data from €169/month. Free project assessment, reply within 1 business day.