BIZTRAC BETA
Accounting and bookkeeping

MERSON AS

Org. no. 989169815 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 668,000
Incorporated 2005
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

MERSON AS is registered as a limited company in Larvik, Vestfold with organisation number 989169815. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Konsulenttjenester innenfor økonomi, regnskap, organisering og ledelse, og annet som hører naturlig inn under dette, samt deltakelse i annen virksomhet og investering i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 668,000
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns MERSON AS?

OVE HAUGEN
MERSON AS
NOK 0 rev. · NOK −12,000 profit

MERSON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MERSON AS own?

MERSON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MERSON AS

Who owns MERSON AS?

OVE HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of MERSON AS?

MERSON AS had revenue of NOK 0 in 2025.

Who is the general manager of MERSON AS?

Ove Haugen is registered as general manager of MERSON AS.

Where is MERSON AS based?

MERSON AS has its business address in Nevlunghavn.

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.