BIZTRAC BETA
Rental and operating of own or leased real estate

STRØMS HOLDING INVEST AS

Org. no. 993320676 Limited company (AS) Indre Østfold Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 594,000
Equity NOK 2.3m
Incorporated 2008
Share capital NOK 750,000

STRØMS HOLDING INVEST AS is registered as a limited company in Indre Østfold, Østfold with organisation number 993320676. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 750,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer. Investeringer i eiendom, samt kjøp og salg av maskiner og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 594,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 594,000
Equity
NOK 2.3m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns STRØMS HOLDING INVEST AS?

BJØRN INGAR STRØM
STRØMS HOLDING INVEST AS
NOK 3.5m rev. · NOK 594,000 profit

STRØMS HOLDING INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STRØMS HOLDING INVEST AS own?

STRØMS HOLDING INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about STRØMS HOLDING INVEST AS

Who owns STRØMS HOLDING INVEST AS?

BJØRN INGAR STRØM is the largest registered owner, with 100.0%.

What is the revenue of STRØMS HOLDING INVEST AS?

STRØMS HOLDING INVEST AS had revenue of NOK 3.5m in 2024.

Where is STRØMS HOLDING INVEST AS based?

STRØMS HOLDING INVEST AS has its business address in Spydeberg.

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.