BIZTRAC BETA
Retail sale of pharmaceutical products

ELVASTRØM AS

Org. no. 923803033 Limited company (AS) Askøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 1.3m
Incorporated 2019
Share capital NOK 40,000

Signals

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

ELVASTRØM AS is registered as a limited company in Askøy, Vestland with organisation number 923803033. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Eier aksje i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 1.3m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns ELVASTRØM AS?

SARAH MORIYE ADEKOYA
ELVASTRØM AS
NOK 0 rev. · NOK −13,000 profit

ELVASTRØM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does ELVASTRØM AS own?

ELVASTRØM AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

ELVASTRØM AS er morselskap for 1 datterselskap:

Frequently asked questions about ELVASTRØM AS

Who owns ELVASTRØM AS?

SARAH MORIYE ADEKOYA is the largest registered owner, with 35.0%.

What is the revenue of ELVASTRØM AS?

ELVASTRØM AS had revenue of NOK 0 in 2024.

Who is the general manager of ELVASTRØM AS?

Olayiwula Adedotun Adekoya is registered as general manager of ELVASTRØM AS.

Where is ELVASTRØM AS based?

ELVASTRØM AS has its business address in Hetlevik.

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.