BIZTRAC BETA
Rental and operating of own or leased real estate

EKM INVEST AS

Org. no. 890247962 Limited company (AS) Ullensaker Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −821,000
Equity NOK 57.3m
Incorporated 2006
Share capital NOK 15.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−821k kr).

EKM INVEST AS is registered as a limited company in Ullensaker, Akershus with organisation number 890247962. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 15.5m, divided into 15462000 shares. The company's stated purpose is: “Handelsvirksomhet, utleie, investering og forvaltning av fast eiendom. Investering av aksjer og andre verdipapirer, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −821,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −821,000
Equity
NOK 57.3m
Est. value
NOK 392.4m

Financial health · 2024

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

Who owns EKM INVEST AS?

SIGMA GRUPPEN AS
EKM INVEST AS
NOK 0 rev. · NOK −821,000 profit

EKM INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EKM INVEST AS own?

EKM INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about EKM INVEST AS

Who owns EKM INVEST AS?

SIGMA GRUPPEN AS is the largest registered owner, with 33.3%.

What is the revenue of EKM INVEST AS?

EKM INVEST AS had revenue of NOK 0 in 2024.

Where is EKM INVEST AS based?

EKM INVEST AS has its business address in Jessheim.

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.