BIZTRAC BETA
Uoppgitt

A. MUNKHAUGEN AS

Org. no. 933988481 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

A. MUNKHAUGEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933988481. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Virksomhet skal være selv, gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom og annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns A. MUNKHAUGEN AS?

ANDREA MUNKHAUGEN
A. MUNKHAUGEN AS
NOK 0 rev. · NOK 0 profit

A. MUNKHAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A. MUNKHAUGEN AS own?

A. MUNKHAUGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about A. MUNKHAUGEN AS

Who owns A. MUNKHAUGEN AS?

ANDREA MUNKHAUGEN is the largest registered owner, with 100.0%.

What is the revenue of A. MUNKHAUGEN AS?

A. MUNKHAUGEN AS had revenue of NOK 0 in 2024.

Where is A. MUNKHAUGEN AS based?

A. MUNKHAUGEN AS has its business address in Trondheim.

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.