BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

SI-RO INVEST AS

Org. no. 996329046 Limited company (AS) Sandefjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 7.1m
Incorporated 2010
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

SI-RO INVEST AS is registered as a limited company in Sandefjord, Vestfold with organisation number 996329046. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2010. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Import, salg av handelsvarer og utførelse av byggetjenester, samt investering i aksjer, andeler og andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 7.1m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns SI-RO INVEST AS?

SIV KARLSEN MOA
SI-RO INVEST AS
NOK 0 rev. · NOK −9,000 profit

SI-RO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SI-RO INVEST AS own?

SI-RO INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SI-RO INVEST AS

Who owns SI-RO INVEST AS?

SIV KARLSEN MOA is the largest registered owner, with 100.0%.

What is the revenue of SI-RO INVEST AS?

SI-RO INVEST AS had revenue of NOK 0 in 2025.

Where is SI-RO INVEST AS based?

SI-RO INVEST AS has its business address in Sandefjord.

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.