BIZTRAC BETA
Other captive investment companies

SERRAFINA HOLDING AS

Org. no. 912461157 Limited company (AS) Sandefjord Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 8.5m
Incorporated 2013
Share capital NOK 1.1m

Signals

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

SERRAFINA HOLDING AS is registered as a limited company in Sandefjord, Vestfold with organisation number 912461157. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 1.1m, divided into 1001 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 8.5m
Est. value
NOK 7.3m

Financial health · 2025

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

Who owns SERRAFINA HOLDING AS?

ANETTE ERIKSEN
SERRAFINA HOLDING AS
NOK 0 rev. · NOK −7,000 profit

SERRAFINA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SERRAFINA HOLDING AS own?

SERRAFINA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SERRAFINA HOLDING AS

Who owns SERRAFINA HOLDING AS?

ANETTE ERIKSEN is the largest registered owner, with 99.9%.

What is the revenue of SERRAFINA HOLDING AS?

SERRAFINA HOLDING AS had revenue of NOK 0 in 2025.

Where is SERRAFINA HOLDING AS based?

SERRAFINA HOLDING 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.