BIZTRAC BETA
Rental and operating of own or leased real estate

MJÅVANNSTOMTA AS

Org. no. 987059168 Limited company (AS) Kristiansand Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 2.3m
Equity NOK 6.5m
Incorporated 2004
Share capital NOK 2.8m

MJÅVANNSTOMTA AS is registered as a limited company in Kristiansand, Agder with organisation number 987059168. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 2.8m, divided into 233750 shares. The company's stated purpose is: “Utvikle og utleie av eiendommer, samt hva dermed i forbindelse, og herunder også å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 2.3m
Equity
NOK 6.5m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns MJÅVANNSTOMTA AS?

MJÅVANNSPARKEN EIENDOM AS
MJÅVANNSTOMTA AS
NOK 3.6m rev. · NOK 2.3m profit

MJÅVANNSTOMTA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MJÅVANNSTOMTA AS er morselskap for 3 datterselskaper:

Frequently asked questions about MJÅVANNSTOMTA AS

Who owns MJÅVANNSTOMTA AS?

MJÅVANNSPARKEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MJÅVANNSTOMTA AS?

MJÅVANNSTOMTA AS had revenue of NOK 3.6m in 2024.

Who is the general manager of MJÅVANNSTOMTA AS?

Roy Gundersen is registered as general manager of MJÅVANNSTOMTA AS.

Where is MJÅVANNSTOMTA AS based?

MJÅVANNSTOMTA AS has its business address in Kristiansand S.

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.