BIZTRAC BETA
Buying and selling of own real estate

EWO INVEST AS

Org. no. 996932559 Limited company (AS) Nordre Follo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 40,000
Incorporated 2011
Share capital NOK 320,000

Signals

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

EWO INVEST AS is registered as a limited company in Nordre Follo, Akershus with organisation number 996932559. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2011. Registered share capital is NOK 320,000, divided into 3200 shares. The company's stated purpose is: “Investeringer i finansielle instrumenter, selskapsandeler og fast eiendom, og alminnelig forretningsvirksomhet. Selskapet kan også yte konsulent-tjenester innen disse forretningsområdene, samt delta i andre selskaper og virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 40,000
Est. value
NOK 37,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EWO INVEST AS?

BJØRN ARVE THOMASSEN
EWO INVEST AS
NOK 0 rev. · NOK −3,000 profit

EWO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EWO INVEST AS

Who owns EWO INVEST AS?

BJØRN ARVE THOMASSEN is the largest registered owner, with 100.0%.

What is the revenue of EWO INVEST AS?

EWO INVEST AS had revenue of NOK 0 in 2024.

Where is EWO INVEST AS based?

EWO INVEST AS has its business address in Oppegård.

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.