BIZTRAC BETA
Rental and operating of own or leased real estate

MJØSEN FORVALTNING AS

Org. no. 991253270 Limited company (AS) Stange Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 1.6m
Equity NOK 11.9m
Incorporated 2007
Share capital NOK 500,000

MJØSEN FORVALTNING AS is registered as a limited company in Stange, Innlandet with organisation number 991253270. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp og salg samt drift og utleie av fast eiendom. Selskapet kan gjennom aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 1.6m
Equity
NOK 11.9m
Est. value
NOK 13.1m

Financial health · 2025

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

Who owns MJØSEN FORVALTNING AS?

DAG FREDRIK RØHNE
MJØSEN FORVALTNING AS
NOK 4.7m rev. · NOK 1.6m profit

MJØSEN FORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MJØSEN FORVALTNING AS

Who owns MJØSEN FORVALTNING AS?

DAG FREDRIK RØHNE is the largest registered owner, with 100.0%.

What is the revenue of MJØSEN FORVALTNING AS?

MJØSEN FORVALTNING AS had revenue of NOK 4.7m in 2025.

Who is the general manager of MJØSEN FORVALTNING AS?

Dag Fredrik Røhne is registered as general manager of MJØSEN FORVALTNING AS.

Where is MJØSEN FORVALTNING AS based?

MJØSEN FORVALTNING AS has its business address in Ottestad.

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.