BIZTRAC BETA
Legal activities

ADVOKAT MOLLESTAD OPPEGAARD AS

Org. no. 919110937 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 747,000
Equity NOK 5.5m
Incorporated 2017
Share capital NOK 30,000

ADVOKAT MOLLESTAD OPPEGAARD AS is registered as a limited company in Bærum, Akershus with organisation number 919110937. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Advokatvirksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 747,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 747,000
Equity
NOK 5.5m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns ADVOKAT MOLLESTAD OPPEGAARD AS?

HEIDI LILL MOLLESTAD OPPEGAARD
ADVOKAT MOLLESTAD OPPEGAARD AS
NOK 2.9m rev. · NOK 747,000 profit

ADVOKAT MOLLESTAD OPPEGAARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKAT MOLLESTAD OPPEGAARD AS

Who owns ADVOKAT MOLLESTAD OPPEGAARD AS?

HEIDI LILL MOLLESTAD OPPEGAARD is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT MOLLESTAD OPPEGAARD AS?

ADVOKAT MOLLESTAD OPPEGAARD AS had revenue of NOK 2.9m in 2025.

Who is the general manager of ADVOKAT MOLLESTAD OPPEGAARD AS?

Heidi Lill Mollestad Oppegaard is registered as general manager of ADVOKAT MOLLESTAD OPPEGAARD AS.

Where is ADVOKAT MOLLESTAD OPPEGAARD AS based?

ADVOKAT MOLLESTAD OPPEGAARD AS has its business address in Snarøya.

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.