BIZTRAC BETA
Other captive investment companies

MEK INVEST AS

Org. no. 818434332 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 5.2m
Incorporated 2017
Share capital NOK 30,000

Signals

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

MEK INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 818434332. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringsvirksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 5.2m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns MEK INVEST AS?

MONICA ERVIG KJENDALEN
MEK INVEST AS
NOK 0 rev. · NOK −13,000 profit

MEK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEK INVEST AS own?

MEK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEK INVEST AS

Who owns MEK INVEST AS?

MONICA ERVIG KJENDALEN is the largest registered owner, with 100.0%.

What is the revenue of MEK INVEST AS?

MEK INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of MEK INVEST AS?

Monica Ervig Kjendalen is registered as general manager of MEK INVEST AS.

Where is MEK INVEST AS based?

MEK INVEST AS has its business address in Charlottenlund.

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.