EU Industrial Facility Intelligence

Search public industrial facility and reporting records from the European Environment Agency (EEA) Industrial Emissions Portal.

What you get in each row

The Actor reads two official EEA datasets:

• Industrial sites, 2007 to the latest published year (currently 2024): the current EU register behind the Industrial Emissions Portal. Rows (record_type: site) include the site name, facility names, city, country, NUTS region codes, sectors, EEA activity, E-PRTR Annex I activity, reported pollutants and pollutant groups, facility/installation/large-combustion-plant counts, BAT conclusions, latest permit and operation-start dates when published, inspection count, release/transfer/waste data flags, Seveso flag, INSPIRE site ID, and coordinates.
• Legacy E-PRTR facility reports, 2001-2017: rows (

  record_type: facility_report
  ) with facility identifiers, parent company, address, postal code, EEA activity and NACE codes, and coordinates.

dataset: auto (the default) uses the site register unless you choose a reporting year up to 2017, so older saved inputs keep returning the same legacy rows. Every row carries the official query URL, dataset URL, retrieval timestamp, and source attribution. Raw upstream payloads are not passed through.

Example output

{
  "record_type": "site",
  "facility_name": "Example energy plant",
  "country_code": "DE",
  "city": "Hamburg",
  "reporting_year": 2024,
  "sectors": ["ENERGY"],
  "eea_activity": "Electricity and heat production",
  "pollutants": ["Carbon dioxide (CO2)", "Nitrogen oxides (NOX)"],
  "is_seveso_site": false,
  "latitude": 51.2,
  "longitude": 6.8,
  "source": "European Environment Agency Industrial Emissions Portal"
}

Pricing examples

The launch price is $2.50 per 1,000 facility-reporting rows. Apify platform compute and storage charges may apply separately. Small test runs are supported before paid-volume use.

CRM and BI use cases

• Build industrial prospect lists by country, sector, and reporting year.
• Enrich territory planning with facility and parent-company signals.
• Load normalized records into a CRM, warehouse, DuckDB, or BI dashboard.
• Monitor public facility reporting coverage over time.

Why official EEA data

This Actor queries the EEA service directly instead of scraping pages. Every row carries source attribution and retrieval time, making the result easier to audit and refresh.

Input guidance

All filters are optional. Use a two-letter country code such as DE or FR and a reporting year. For industrial sites, filter by a sector keyword such as ENERGY, CHEMICALS, METALS, MINERALS, WASTE, or PAPER; for legacy facility reports use an EEA activity code such as EPER_6.1. A year outside the chosen dataset's coverage is rejected with a message explaining which dataset to use. Set Maximum rows to the smallest amount you need to control spend.

An empty result is a valid response when the selected country, year, or activity has no published matching records. It does not mean the Actor failed; try the broad query first and then add filters one at a time.

Reliability and billing

• Temporary source errors (timeouts, rate limits, 5xx responses) are retried automatically with backoff before a run gives up.
• Rows are published only after the source query finishes. If the official source stays unavailable, the run fails with a clear message and no rows are delivered or charged.
• Rows are de-duplicated across result pages, so you never pay twice for the same record.
• The Actor respects your maximum cost per run: it fetches only as many rows as your budget allows and says so in the status message and RUN_SUMMARY.

Important limitations

This is a public reporting dataset, not legal, compliance, environmental, safety, or investment advice. Coverage and field availability can vary by country and reporting year. Do not infer that a facility is compliant or non-compliant from this output.

Source: EEA Industrial Emissions Portal dataset.

Support

For a run problem, open an issue from this Actor's Apify page and include the run ID, sanitized input, timestamp, and first relevant log message. Never share Apify tokens or private customer data. For commercial or integration questions, contact Arclay at https://arclay.tn. Target response time is two business days.