# Euronext Oslo Regulated News (`nexgenwatch/euronext-oslo-regulated-news`) Actor

One record per regulated Euronext Oslo announcement — issuer, title, category, topic, timestamp, official archive link. Disclosure facts only; the announcement body is never fetched or stored (press-family posture).

- **URL**: https://apify.com/nexgenwatch/euronext-oslo-regulated-news.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** News, Automation, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $13.40 / 1,000 registry_records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 🔔 Euronext Oslo Regulated News

One record per regulated Euronext Oslo announcement — issuer, title, category, topic, timestamp, official archive link. Disclosure facts only; the announcement body is never fetched or stored (press-family posture).

Public, robots-honoured.

Output is one `euronext_oslo_announcement` row per result; billing is pay-per-event, the value event being one registry_record (a $0.02 start fee per run, then $0.02 per registry_record). Source: live.euronext.com.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

**Who buys this**

Buyers usually search for **Euronext Oslo** or **Euronext Oslo announcements**.

- Investors, analysts and IR teams following Euronext Oslo.
- Compliance and data teams tracking Euronext Oslo announcements for a watchlist of issuers.
- Researchers and journalists building dated disclosure records.

### 📊 Sample Output

[![Euronext Oslo Regulated News sample output — a table of real registry_record rows (issuer, title, category, topic) from run CtKeOVN38zIWbWuLP on build 0.1.9](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/euronext-oslo-regulated-news-sample-nw)](https://apify.com/nexgenwatch/euronext-oslo-regulated-news?fpr=2ayu9b)

Real rows from run `CtKeOVN38zIWbWuLP` on build 0.1.9 (2026-09-24), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

| issuer | title | category | topic | released_at | official_link |
|---|---|---|---|---|---|
| PROSAFE | Financial calendar | 60101030 Oil Equipment and Services | Additional regulated information required to be disclosed under the la | 24 Sep 2026 16:07 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| 2020 BULKERS | Major shareholding notification - correction | 50206030 Marine Transportation | Major shareholding notifications | 24 Sep 2026 16:04 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| HIMALAYA SHIPPING LTD | Shareholder Disclosure Notificatio | 50206030 Marine Transportation | Major shareholding notifications | 24 Sep 2026 16:00 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| Fana Sparebank | Fana Sparebank - utvidelse av FSB51 PRO |  | Annen informasjonspliktig regulatorisk informasjon | 24 Sep 2026 15:50 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| 2020 BULKERS | Major Shareholding Notification | 50206030 Marine Transportation | Major shareholding notifications | 24 Sep 2026 15:28 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| Atlantic Sapphire ASA | Atlantic Sapphire ASA: Increase of Bridge Loan | 45102010 Farming, Fishing, Ranching and Plantations | Additional regulated information required to be disclosed under the la | 24 Sep 2026 15:21 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| VENTURA OFFSHORE HOLDING LTD. | Ventura Offshore Holding Ltd.: SSV Catarina Contract Amendment for Add | 60101015 Offshore Drilling and Other Services | Non-regulatory press releases | 24 Sep 2026 15:10 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |
| Ventura Offshore Midco Ltd | Ventura Offshore Midco Ltd.: SSV Catarina – Contract Amendment for Add |  | Non-regulatory press releases | 24 Sep 2026 15:10 CEST | https://live.euronext.com/en/markets/oslo/equities/company-news |

The run finished with the status message: `NORMAL: 47 unique rows (0 duplicates collapsed). billable=47`

### ✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`):

- `record_type` (string) — e.g. `euronext_oslo_announcement`
- `issuer` (string/null) — e.g. `PROSAFE`
- `title` (string/null) — e.g. `Financial calendar`
- `category` (string/null) — e.g. `60101030 Oil Equipment and Services`
- `topic` (string/null) — e.g. `Additional regulated information required to be disclosed under the laws of a Me`
- `released_at` (string/null) — e.g. `24 Sep 2026 16:07 CEST`
- `official_link` (string/null) — e.g. `https://live.euronext.com/en/markets/oslo/equities/company-news`
- `source` (string/null) — e.g. `euronext-oslo-regulated-news`
- `release_date` (string/null) — null in every sample row
- `source_url` (string/null) — e.g. `https://live.euronext.com/en/markets/oslo/equities/company-news`
- `observed_at` (string/null) — e.g. `2026-09-24T15:49:47Z`
- `terminal` (string/integer/null) — null in every sample row
- `reported_total` (string/integer/null) — null in every sample row
- `raw_seen` (string/integer/null) — null in every sample row
- `duplicates` (string/integer/null) — null in every sample row
- `unique_found` (string/integer/null) — null in every sample row
- `delivered` (string/integer/null) — null in every sample row
- `scope` (string/integer/null) — null in every sample row
- `note` (string/integer/null) — null in every sample row

**✅ What you get**

- `record_type` (string) — e.g. `euronext_oslo_announcement`
- `issuer` (string/null) — e.g. `PROSAFE`
- `title` (string/null) — e.g. `Financial calendar`
- `category` (string/null) — e.g. `60101030 Oil Equipment and Services`
- `topic` (string/null) — e.g. `Additional regulated information required to be disclosed under the laws of a Me`
- `released_at` (string/null) — e.g. `24 Sep 2026 16:07 CEST`
- `official_link` (string/null) — e.g. `https://live.euronext.com/en/markets/oslo/equities/company-news`
- `source` (string/null) — e.g. `euronext-oslo-regulated-news`
- `release_date` (string/null) — null in every sample row
- `source_url` (string/null) — e.g. `https://live.euronext.com/en/markets/oslo/equities/company-news`
- `observed_at` (string/null) — e.g. `2026-09-24T15:46:49Z`
- `terminal` (string/integer/null) — null in every sample row
- `reported_total` (string/integer/null) — null in every sample row
- `raw_seen` (string/integer/null) — null in every sample row
- `duplicates` (string/integer/null) — null in every sample row
- `unique_found` (string/integer/null) — null in every sample row
- `delivered` (string/integer/null) — null in every sample row
- `scope` (string/integer/null) — null in every sample row
- `note` (string/integer/null) — null in every sample row

**What you get**

One `registry_record` per entity, deduplicated on the source-native id. Fields the source does not publish are honest `null`. A `run_receipt` row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

### ⚙️ Sample inputs

**1. Quick start — the Store example (this is what the sample above came from)**

```json
{
  "maxRecords": 50,
  "maxPages": 5
}
```

The sample run charged exactly: 1 × $0.02 apify-actor-start + 47 × $0.02 registry_record = **$0.96** on the Free tier — every delivered row was billed.
If you leave `maxRecords` out, the run delivers at most 50 rows (the schema default); pass a number up to 500000 for a bigger export. An explicit value is always honoured up to that maximum.

**2. A smaller, narrowed run**

```json
{
  "maxRecords": 5,
  "maxPages": 5
}
```

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

**3. A full-size run**

```json
{
  "maxRecords": 5000,
  "maxPages": 5
}
```

Up to 5000 rows — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many; `maxRecords` goes up to 500000.

**4. A filtered run**

```json
{
  "maxRecords": 10,
  "maxPages": 3,
  "searchText": "Equinor"
}
```

Regulated announcements whose issuer or headline matches `Equinor` (Euronext's listing filter applies before paging; `fieldMatch.released_at` takes a date or date range). The public archive holds roughly the most recent month; the source applies this filter **before** paging and before the `maxRecords` cap, so a match deep in the dataset is found, the reconciled count is the matched count, and only delivered matches are billed. A confirmed no-match ends `EMPTY_SELECTION` with nothing charged.

### 🧾 JSON sample record

One real record from run `CtKeOVN38zIWbWuLP`, exactly as it lands in the dataset (emails masked, long text shortened):

```json
{
  "record_type": "euronext_oslo_announcement",
  "issuer": "PROSAFE",
  "title": "Financial calendar",
  "category": "60101030 Oil Equipment and Services",
  "topic": "Additional regulated information required to be disclosed under the laws of a Member State",
  "released_at": "24 Sep 2026 16:07 CEST",
  "official_link": "https://live.euronext.com/en/markets/oslo/equities/company-news",
  "source": "euronext-oslo-regulated-news",
  "release_date": null,
  "source_url": "https://live.euronext.com/en/markets/oslo/equities/company-news",
  "observed_at": "2026-09-24T15:49:47Z"
}
```

### 🔧 How it works

**Source.** The actor reads live.euronext.com — endpoints: `https://live.euronext.com/en/markets/oslo/equities/company-news`. Public pages and feeds only; nothing behind a login.

**Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

**Charging.** Each registry_record is charged at the moment it is pushed (`registry_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

**🔧 How it works**

**How it behaves**

The server-rendered Oslo company-news archive is read and paged conservatively (?page). Rows are canaried on the 5-column shape; issuer/title/category/topic/timestamp captured; the body is never fetched. A structure change on page 0 fails loud.

**Source**

`https://live.euronext.com/en/markets/oslo/equities/company-news`

**What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

### 💰 Pricing example

| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| registry_record (`registry_record`) | $0.02 | $0.018 | $0.016 | $0.0134 |

Worked at the live Free-tier price:

- 8 registry_records: $0.02 start + 8 × $0.02 = **$0.18**
- 25 registry_records: $0.02 start + 25 × $0.02 = **$0.52**
- 50 registry_records: $0.02 start + 50 × $0.02 = **$1.02**

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: `NORMAL: 47 unique rows (0 duplicates collapsed). billable=47`. `maxRecords` is a hard ceiling on what is delivered and billed, never a target.

### ⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by live.euronext.com. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

### ❓ FAQ

**Q: Do I need an API key or a login?**\
A: No. The source (live.euronext.com) is read logged-out; the input schema has no key field and the actor carries no secrets.

**Q: Why did my run return 0 rows?**\
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

**Q: How many rows can one run return?**\
A: Up to `maxRecords` (default 50). Raise the cap for a bigger run; you pay per delivered row.

**Q: How fresh is the data?**\
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

**Q: What formats can I export?**\
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

**Q: How is this different from the other NexGen Watch actors actors?**\
A: Same output shape and billing model; this one covers live.euronext.com. The siblings under **Related Actors** cover the other sources or slices — run several on one schedule for a combined feed.

**Q: Are there rate limits?**\
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

### 🆘 Troubleshooting

- **Run FAILED with BLOCKED** → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
- **Status says CAPPED** → your cap (`maxRecords`) was reached → raise it for a bigger run.
- **Input validation error on start** → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
- **Run TIMED-OUT** → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

### 🔗 Related Actors

- [EU Ecolabel Licensed Products & Services](https://apify.com/nexgenwatch/eu-ecolabel?fpr=2ayu9b) — One structured ecolabel_record per awarded EU Ecolabel licence-line — from the official European Commission open-data export, keyless and logged-out
- [EU (EMA) Medicine Shortages Catalogue](https://apify.com/nexgenwatch/eu-medicines-shortage?fpr=2ayu9b) — One structured medicine_shortage_record per entry in the European Medicines Agency's public catalogue of medicine shortages assessed by the Agency —…
- [EU Transparency Register Organisations](https://apify.com/nexgenwatch/eu-transparency-register-organisations?fpr=2ayu9b) — One structured organisation_record per interest representative in the EU Transparency Register — from the official current full XML export, keyless a…
- [USDA FDC Analytical Sub-Sample Results](https://apify.com/nexgenwatch/fdc-analytical-subsample-results?fpr=2ayu9b) — Structured laboratory sub-sample measurement records from USDA FoodData Central, read directly from the official FDC full-CSV data dump (sub_sample_r…
- [USDA FDC Calorie Conversion Factors](https://apify.com/nexgenwatch/fdc-calorie-conversion-factors?fpr=2ayu9b) — Delivers the published USDA FoodData Central *calorie conversion factors* — one calorie_factor_record per row of the food_calorie_conversion_factor.c…
- [USDA FDC Sample Provenance Graph](https://apify.com/nexgenwatch/fdc-sample-provenance-graph?fpr=2ayu9b) — The provenance / traceability graph behind USDA FoodData Central foods — how a sample food links to its sub-samples and to the market acquisition it…
- 🏢 **About NexGen Watch** — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b).

### ⭐ Found this useful?

If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/euronext-oslo-regulated-news?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab — every one is read.

# Actor input Schema

## `maxRecords` (type: `integer`):

maxRecords (buyer bound).

## `searchText` (type: `string`):

Text Euronext's own listing filter matches against issuer name and headline before paging (e.g. 'Equinor'). Found across the whole archive, not just the first rows.

## `fieldMatch` (type: `object`):

Filters Euronext applies before paging, as {"column": "value"} using these output columns: issuer (text), released_at (YYYY-MM-DD or YYYY-MM-DD..YYYY-MM-DD). An unknown column fails the run before any fetch.

## `maxPages` (type: `integer`):

maxPages (buyer bound).

## `userAgent` (type: `string`):

userAgent.

## Actor input object example

```json
{
  "maxRecords": 50,
  "maxPages": 5
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 50,
    "maxPages": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/euronext-oslo-regulated-news").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxRecords": 50,
    "maxPages": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/euronext-oslo-regulated-news").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 50,
  "maxPages": 5
}' |
apify call nexgenwatch/euronext-oslo-regulated-news --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/euronext-oslo-regulated-news"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/onVVdvmxG8EmHMYHc/builds/Qi4XXdk1KHoU48hVl/openapi.json