TankTerminals.com — Global Tank Terminal Directory

One product owns the commercial tank-storage estate the way asset maps never will. TankTerminals.com, published by INSIGHTS GLOBAL TankTerminals B.V. of Breda, is a market-intelligence database describing 13,000-plus tank terminals and production facilities organized across 2,420 ports and cities worldwide. Scope runs past pure storage into seven facility classes: commercial and captive tank terminals, petroleum refineries, crude petroleum export terminals, chemical sites, olefin plants, LNG liquefaction facilities and vegetable-oil refineries.

Every facility carries a Terminal Fact Sheet — identity and placement, total tank capacity, tank count and size range, average capacity per tank, berth count, stored products, modal connections, facility contact details and up to three named managers with phone numbers and email addresses. Extended panels surround that spine: throughput, pump speed, berth occupancy, vessel turnaround time, visit frequencies, ship types and tank turns measured at terminal, berth, country and region grain; a Capacity Evolution and Projection series pairing recorded history with forward estimates; and weekly import/export volumes in barrels for crude oil, LPG, LNG, gasoline, diesel and chemicals.

Inside Datadory's Oil & Gas Storage & Transportation catalog it is one of six primary slice members and the only one whose unit of observation is the commercial terminal itself — geospatial layers in the same slice stop at a polygon, while this record attaches steel, water and named people to the asset. Get a sample of this dataset cut to the regions, products and facility classes you track.

One record per facility, flattened to a fact-sheet row — the shape below mirrors the documented fields:

# Terminal Fact Sheet — one record per facility (illustrative structure)
terminal_name       Botlek Fuels & Chemicals Terminal
location            Rotterdam, Netherlands
tank_capacity       855000            # total, as reported on the fact sheet
tank_count          74
tank_size_range     2500-35000        # smallest to largest individual tank
avg_tank_capacity   11554
berth_count         9
stored_products     gasolines; diesel; jet fuel; chemicals
delivery_methods      marine; pipeline; truck
facility_contact    switchboard + general inbox
manager_contacts    3 named managers — phone + email apiece

(Illustrative structure — request the sample for real rows.) Three things worth noticing. First, manager_contacts reaches named humans rather than a switchboard, which is what turns the directory from a map into a route to terminal decision-makers. Second, stored_products and delivery_methods ride on the same row as capacity, so a screen for "chemical-capable, marine-served sites above half a million cubic metres" is one filter pass instead of a stitching job. Third, berth_count sitting beside tank_capacity separates marine-served hubs from land-locked stock — the distinction every export-window analysis quietly depends on.

Eleven documented fields carry each Terminal Fact Sheet, defined below. Two do the heavy lifting: tank_capacity is the screening column behind every capacity-league chart, and location keys cleanly onto any port master table you already maintain, which makes joins into AIS movement data or port-call statistics a one-line merge. manager_contacts has no equivalent anywhere else in the slice.

Definitions are drawn from the product's own documentation rather than authenticated fact sheets, so treat the dictionary as high-confidence shape with per-column semantics confirmed against delivered rows when your sample is prepared — the same pass locks column naming for your pipeline.

• Geography: worldwide, organized across 2,420 ports and cities and searchable by region, country, port, hub or continent — the frame reaches the Asian storage buildout and Middle East export complexes that national datasets never cross.
• Temporal: a living database rather than a frozen extract. The Capacity Evolution and Projection panel pairs recorded history with forward estimates, so capacity screens can run forward, not just backward; archive depth is confirmed per window when your sample is scoped.
• Granularity: one fact sheet per facility, extending down to berth-level logistics — throughput, occupancy, turnaround and tank turns can be read at terminal, berth, country or region grain. It is the only slice member where a single record carries both the tanks and the water.

On Datadory's 0–10 quality rubric the record scores 5, against a 7.81 average across the 1,744 cataloged datasets — the discount reflects inferred field definitions and unverified archive depth, not coverage breadth, which nothing else in the industry matches at this grain.

API, files, or your warehouse. Daily, weekly, or hourly.

You pick the channel and the cadence; the field dictionary above travels unchanged across all three. Bulk files suit overnight warehouse loads, structured payloads suit event-driven pipelines, and the fact-sheet table lands in spreadsheet- and SQL-friendly shapes for analysts who live in a BI tool. Because the grain never changes, switching cadence later is a settings conversation, not a re-integration project.

• Storage-capacity benchmarking — rank terminals by capacity, tank count and berth count within any port range; the 2,420-port frame makes "top ten fuels hubs in Southeast Asia" a query rather than a research project.
• Supply-side screening — capacity and ownership intelligence feeding midstream theses, relevance-tagged for investor workflows: who holds the barrels, where, and at what berth depth.
• Flow studies — weekly import/export volumes in barrels for crude, LPG, LNG, gasoline, diesel and chemicals show which hubs physically move product, not just which ones store it.
• Business development — up to three named managers per fact sheet routes outreach to the people who sign storage contracts, filtered by product and geography before the first call.
• Competitive footprint mapping — track which operator runs which berths in which ports, and watch a rival's storage position change as capacity revisions land.
• Cited research — journalists and academics anchor energy-security arguments to facility factsheets with clean commercial attribution.

Market researchers & consultants (relevance 2, the slice's highest for this record) benchmark commercial terminal capacity, berths and throughput across 2,420 ports — the tagged use case reads plainly: 13k-18k terminal coverage; patterns in market researchers use cases. Investors & quant researchers (relevance 1) feed supply-side screens with capacity and ownership intelligence; see investors quants use cases. Sales & growth teams work the manager-contact columns as a pre-filtered route into terminal decision-makers. Developers & builders join the fact-sheet table onto geospatial layers to give every polygon a commercial payload; wiring notes in developers builders use cases. Journalists, academics & students cite facility factsheets where free layers offer nothing citable.

• OGIM — Oil and Gas Infrastructure Mapping database (EDF) — the free geospatial counterweight: 3,661 petroleum terminals across 152 countries with no throughput, occupancy or contacts attached (OGIM).
• HIFLD Petroleum Terminals (POL Terminals) — 2,302 operable US POL terminals with 50 attributes each; deep at home, silent past the border (HIFLD).
• OpenStreetMap — Pipeline & Storage Facility Features — roughly 867,000 storage-tank features edited in near-realtime, carrying geometry but no capacity figures (OSM slice).
• PUDL Raw EIA Bulk API Data (archived snapshots) — weekly US stocks and import histories back to April 2004; the flow-time companion to this snapshot-of-record (PUDL).
• Glossary notes — what storage capacity measures, how refinery throughput differs from terminal throughput, and where an LNG terminal inventory fits.

Two honesty notes before you request a sample. The publisher states both "13,000-plus tank terminal facilities" and "18,000-plus terminals and production facilities" on its own pages (earlier marketing cited 7,000), so treat 13,000-plus as the floor and confirm the current count against delivered rows. And because field definitions are inferred from product documentation, per-column semantics are locked against live records during sample preparation. Full slice ranking sits on the oil gas storage transportation data hub.