BIZTRAC BETA
Other captive investment companies

MUNO AS

Org. no. 989190415 Limited company (AS) Vestby Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −22,000
Equity NOK 6.1m
Incorporated 2005
Share capital NOK 100,000

Signals

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

MUNO AS is registered as a limited company in Vestby, Akershus with organisation number 989190415. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 2900 shares. The company's stated purpose is: “Eie og investere i aksjer samt deltagelse i andre virksomheter. I tillegg skal selskapet drive med musikkarbeid, instruksjon og arrangeringsformidling.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 6.1m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns MUNO AS?

STEINAR KRISTOFFER FORFANG
MUNO AS
NOK 0 rev. · NOK −22,000 profit

MUNO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUNO AS own?

MUNO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUNO AS

Who owns MUNO AS?

STEINAR KRISTOFFER FORFANG is the largest registered owner, with 100.0%.

What is the revenue of MUNO AS?

MUNO AS had revenue of NOK 0 in 2024.

Who is the general manager of MUNO AS?

Steinar Kristoffer Forfang is registered as general manager of MUNO AS.

Where is MUNO AS based?

MUNO AS has its business address in Vestby.

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.