BIZTRAC BETA
Rental and operating of own or leased real estate

EKVATOR EIENDOM AS

Org. no. 898534472 Limited company (AS) Horten Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −53,000
Equity NOK 15.5m
Incorporated 2012
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−53k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EKVATOR EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 898534472. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 500,000, divided into 280 shares. The company's stated purpose is: “Kjøp og salg av aksjer, andre selskapsandeler, verdipapirer og fast eiendom, samt alt som står i naturlig sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −53,000
Equity
NOK 15.5m
Est. value
NOK 14.2m

Financial health · 2024

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

Who owns EKVATOR EIENDOM AS?

JMC AS
EKVATOR EIENDOM AS
· NOK −53,000 profit

EKVATOR EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does EKVATOR EIENDOM AS own?

EKVATOR EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EKVATOR EIENDOM AS

Who owns EKVATOR EIENDOM AS?

JMC AS is the largest registered owner, with 35.7%.

Who is the general manager of EKVATOR EIENDOM AS?

Jon Patrik Mørk is registered as general manager of EKVATOR EIENDOM AS.

Where is EKVATOR EIENDOM AS based?

EKVATOR EIENDOM AS has its business address in Horten.

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.