BIZTRAC BETA
Rental and operating of own or leased real estate

JOHAN S. SVENDSEN AS

Org. no. 989131494 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −105,000
Equity NOK 2.8m
Incorporated 2005
Share capital NOK 27.3m

Signals

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

JOHAN S. SVENDSEN AS is registered as a limited company in Bærum, Akershus with organisation number 989131494. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 27.3m, divided into 401 shares. The company's stated purpose is: “Erverv, utvikling og forvaltning av fast eiendom, samt deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −105,000
Equity
NOK 2.8m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns JOHAN S. SVENDSEN AS?

EIFFEL EIENDOM AS
JOHAN S. SVENDSEN AS
· NOK −105,000 profit

JOHAN S. SVENDSEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JOHAN S. SVENDSEN AS own?

JOHAN S. SVENDSEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about JOHAN S. SVENDSEN AS

Who owns JOHAN S. SVENDSEN AS?

EIFFEL EIENDOM AS is the largest registered owner, with 38.4%.

Who is the general manager of JOHAN S. SVENDSEN AS?

Erik Cato Ender is registered as general manager of JOHAN S. SVENDSEN AS.

Where is JOHAN S. SVENDSEN AS based?

JOHAN S. SVENDSEN AS has its business address in Lysaker.

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.