BIZTRAC BETA
Uoppgitt

MØSNUKEN HOLDING AS

Org. no. 934503775 Limited company (AS) Bjørnafjorden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −69
Equity NOK 823,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

MØSNUKEN HOLDING AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 934503775. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer, kjøp og salg av aksjer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −69 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −69
Equity
NOK 823,000
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns MØSNUKEN HOLDING AS?

JØRN ARE LUND
MØSNUKEN HOLDING AS
NOK 0 rev. · NOK −69 profit

MØSNUKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MØSNUKEN HOLDING AS own?

MØSNUKEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MØSNUKEN HOLDING AS

Who owns MØSNUKEN HOLDING AS?

JØRN ARE LUND is the largest registered owner, with 100.0%.

What is the revenue of MØSNUKEN HOLDING AS?

MØSNUKEN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of MØSNUKEN HOLDING AS?

Jørn Are Lund is registered as general manager of MØSNUKEN HOLDING AS.

Where is MØSNUKEN HOLDING AS based?

MØSNUKEN HOLDING AS has its business address in Os.

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.