BIZTRAC BETA
Wholesale of beverages

STRØM AS

Org. no. 970923292 Limited company (AS) Nittedal Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 50.2m
Operating profit NOK −2.1m
Equity NOK 9.3m
Incorporated 1994
Share capital NOK 350,000

Signals

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

STRØM AS is registered as a limited company in Nittedal, Akershus with organisation number 970923292. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 1994. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Agenturvirksomhet og handel, samt hva dermed står i forbindelse, herunder deltagelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.2m in revenue and NOK −2.1m in operating profit.

Key figures · 2024

Revenue
NOK 50.2m
Operating profit
NOK −2.1m
Equity
NOK 9.3m
Est. value
NOK 20.8m

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.5%
Good
Equity as a share of total capital

Who owns STRØM AS?

ANORA GROUP OYJ
STRØM AS
NOK 50.2m rev. · NOK −2.1m profit

STRØM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STRØM AS er morselskap for 6 datterselskaper:

Frequently asked questions about STRØM AS

Who owns STRØM AS?

ANORA GROUP OYJ is the largest registered owner, with 100.0%.

What is the revenue of STRØM AS?

STRØM AS had revenue of NOK 50.2m in 2024.

Who is the general manager of STRØM AS?

Aina Mee Myhre is registered as general manager of STRØM AS.

Where is STRØM AS based?

STRØM AS has its business address in Hagan.

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.