BIZTRAC BETA
Intermediation service activities for business support service activities n.e.c.

MERCURIENNE AS

Org. no. 987487844 Limited company (AS) Frogn Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −143,000
Equity NOK 6.2m
Incorporated 2004
Share capital NOK 450,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−143k kr).

MERCURIENNE AS is registered as a limited company in Frogn, Akershus with organisation number 987487844. The business is classified under intermediation service activities for business support service activities n.e.c. (NACE 82.400). The company was incorporated in 2004. Registered share capital is NOK 450,000, divided into 1000 shares. The company's stated purpose is: “Drive konsulent- og rådgivningsvirksomhet, samt agenturvirksomhet, samt delta i annen virksomhet ved tegning av aksjer i, foreta investeringer i eller delta i drift av andre selskaper, samt annet som hører naturlig herunder.”.

Key figures · 2024

Operating profit
NOK −143,000
Equity
NOK 6.2m
Est. value
NOK 9.0m

Financial health · 2024

Liquidity
920.19
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns MERCURIENNE AS?

SVEN TORE OTTESEN
MERCURIENNE AS
· NOK −143,000 profit

MERCURIENNE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MERCURIENNE AS own?

MERCURIENNE AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MERCURIENNE AS

Who owns MERCURIENNE AS?

SVEN TORE OTTESEN is the largest registered owner, with 100.0%.

Who is the general manager of MERCURIENNE AS?

Sven Tore Ottesen is registered as general manager of MERCURIENNE AS.

Where is MERCURIENNE AS based?

MERCURIENNE AS has its business address in Drøbak.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.