BIZTRAC BETA
Rental and operating of own or leased real estate

STRØM EIENDOM AS

Org. no. 979359489 Limited company (AS) Nærøysund Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 707,000
Operating profit NOK −59,000
Equity NOK 1.3m
Incorporated 1997
Share capital NOK 300,000

Signals

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

STRØM EIENDOM AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 979359489. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Investere i, og å leie ut fast eiendom. Selskapet kan som eier eller deltaker ha interesser i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 707,000 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 707,000
Operating profit
NOK −59,000
Equity
NOK 1.3m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns STRØM EIENDOM AS?

HÅVARD WILLIAM STRØM
STRØM EIENDOM AS
NOK 707,000 rev. · NOK −59,000 profit

STRØM EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRØM EIENDOM AS

Who owns STRØM EIENDOM AS?

HÅVARD WILLIAM STRØM is the largest registered owner, with 83.3%.

What is the revenue of STRØM EIENDOM AS?

STRØM EIENDOM AS had revenue of NOK 707,000 in 2024.

Who is the general manager of STRØM EIENDOM AS?

Trond Strøm is registered as general manager of STRØM EIENDOM AS.

Where is STRØM EIENDOM AS based?

STRØM EIENDOM AS has its business address in Kolvereid.

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.