BIZTRAC BETA
COMPANY REGISTER PROFILE
928795152 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

MK FORVALTNING AS

Org. no. 928795152 Limited company (AS) Ringsaker Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 7.3m
Incorporated 2022
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

MK FORVALTNING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 928795152. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom. Selskapet kan også drive med utleie av personell og andre tjenester innen kraning, transport, bygg og anlegg, samt virksomhet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 7.3m
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns MK FORVALTNING AS?

MORTEN SVENMOEN
MK FORVALTNING AS
· NOK −11,000 profit

MK FORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MK FORVALTNING AS

Who owns MK FORVALTNING AS?

MORTEN SVENMOEN is the largest registered owner, with 100.0%.

Who is the general manager of MK FORVALTNING AS?

Morten Svenmoen is registered as general manager of MK FORVALTNING AS.

Where is MK FORVALTNING AS based?

MK FORVALTNING AS has its business address in Brumunddal.

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.