BIZTRAC BETA
Rental and operating of own or leased real estate

MUNIN INVEST AS

Org. no. 989263838 Limited company (AS) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 210,000
Operating profit NOK 100,000
Equity NOK 5.4m
Incorporated 2005
Share capital NOK 2.9m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MUNIN INVEST AS is registered as a limited company in Tromsø, Troms with organisation number 989263838. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 810 shares. The company's stated purpose is: “Investere i verdipapirer og eiendom samt kunne delta i annen forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 210,000 in revenue and NOK 100,000 in operating profit.

Key figures · 2024

Revenue
NOK 210,000
Operating profit
NOK 100,000
Equity
NOK 5.4m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns MUNIN INVEST AS?

DIN REVISOR TROMSØ AS
MUNIN INVEST AS
NOK 210,000 rev. · NOK 100,000 profit

MUNIN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MUNIN INVEST AS

Who owns MUNIN INVEST AS?

DIN REVISOR TROMSØ AS is the largest registered owner, with 100.0%.

What is the revenue of MUNIN INVEST AS?

MUNIN INVEST AS had revenue of NOK 210,000 in 2024.

Who is the general manager of MUNIN INVEST AS?

Dan Andreassen is registered as general manager of MUNIN INVEST AS.

Where is MUNIN INVEST AS based?

MUNIN INVEST AS has its business address in Tromsø.

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.