biztrac. BETA
COMPANY REGISTER PROFILE
927047594 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MKE AS

Org. no. 927047594 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK −373,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−373k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

MKE AS is registered as a limited company in Oslo, Oslo with organisation number 927047594. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og forvalte investeringer som gjøres.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▼ −85 %
Equity
NOK −373,000
▼ −6 %

Financial health · 2025

Liquidity
4951.86
Very good
Current assets ÷ current liabilities
Profitability
1.7%
Weak
Return on total assets
Solidity
-90.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MKE AS?

MKE AS
NOK 0 rev. · NOK −5,000 profit

MKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MKE AS own?

MKE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MKE AS

Who owns MKE AS?

Magnus Kalvå-Eldegard is the largest registered owner, with 100.0%.

What is the revenue of MKE AS?

MKE AS had revenue of NOK 0 in 2025.

Who is the general manager of MKE AS?

Magnus Kalvå-Eldegard is registered as general manager of MKE AS.

Where is MKE AS based?

MKE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.