biztrac. BETA
COMPANY REGISTER PROFILE
995763249 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

ESØS AS

Org. no. 995763249 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −37,000
Equity NOK 16.1m
Incorporated 2010
Share capital NOK 100,000

Signals

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

ESØS AS is registered as a limited company in Oslo, Oslo with organisation number 995763249. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie selskaper eller andeler av selskaper med virksomhet relatert til entreprenørvirksomhet, salg og konsulentvirksomhet, samt hva hermed står i forbindelse. Selskapet kan videre eie og drive fast eiendom. Selskapet kan ved aksjeinnskudd, lån, garantistillelse eller på annen måte delta i annen næringsvirksomhet.”.

Key figures · 2025

Operating profit
NOK −37,000
▼ −39 %
Equity
NOK 16.1m
▲ +3 %
Est. value
NOK 12.9m

Financial health · 2025

Liquidity
204.34
Very good
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns ESØS AS?

ESØS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ESØS AS own?

ESØS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESØS AS

Who owns ESØS AS?

Øyvind Strøm is the largest registered owner, with 50.0%.

Who is the general manager of ESØS AS?

Øyvind Strøm is registered as general manager of ESØS AS.

Where is ESØS AS based?

ESØS 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.