BIZTRAC BETA
COMPANY REGISTER PROFILE
971592737 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

EWI AS

Org. no. 971592737 Limited company (AS) Bærum Incorporated 1994 Active
Ownership graph ↗
Operating profit NOK −2.3m
Equity NOK 73.3m
Incorporated 1994
Share capital NOK 75,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,3 mill kr).

EWI AS is registered as a limited company in Bærum, Akershus with organisation number 971592737. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1994. Registered share capital is NOK 75,000, divided into 500 shares. The company's stated purpose is: “Selskapets formål er investeringsaktivitet samt finansiell konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −2.3m
▼ −10 %
Equity
NOK 73.3m
▲ +13 %
Est. value
NOK 81.1m

Financial health · 2025

Liquidity
25.09
Very good
Current assets ÷ current liabilities
Profitability
20.9%
Very good
Return on total assets
Solidity
96.0%
Very good
Equity as a share of total capital

Who owns EWI AS?

EWI AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EWI AS own?

EWI AS holds stakes in 19 companies:

See the full ownership structure →

Frequently asked questions about EWI AS

Who owns EWI AS?

EYVIND WIDTH is the largest registered owner, with 60.0%.

Where is EWI AS based?

EWI AS has its business address in Snarøya.

Property

Business address Framnesveien 16, 1367 Snarøya
Cadastral unit 3201-43/566/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.