BIZTRAC BETA
Uoppgitt

SIV MERETE FINSTAD HOLDING AS

Org. no. 925250457 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 108,000
Incorporated 2020
Share capital NOK 125,000

Signals

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

SIV MERETE FINSTAD HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 925250457. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 125,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 108,000
Est. value
NOK 276,000

Financial health · 2025

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

Who owns SIV MERETE FINSTAD HOLDING AS?

SIV MERETE FINSTAD
SIV MERETE FINSTAD HOLDING AS
NOK 0 rev. · NOK −17,000 profit

SIV MERETE FINSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIV MERETE FINSTAD HOLDING AS own?

SIV MERETE FINSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIV MERETE FINSTAD HOLDING AS

Who owns SIV MERETE FINSTAD HOLDING AS?

SIV MERETE FINSTAD is the largest registered owner, with 100.0%.

What is the revenue of SIV MERETE FINSTAD HOLDING AS?

SIV MERETE FINSTAD HOLDING AS had revenue of NOK 0 in 2025.

Where is SIV MERETE FINSTAD HOLDING AS based?

SIV MERETE FINSTAD HOLDING AS has its business address in Søgne.

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.