BIZTRAC BETA
Other captive investment companies

REKKEVIK HOLDING AS

Org. no. 912460894 Limited company (AS) Larvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 10.3m
Incorporated 2013
Share capital NOK 800,000

Signals

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

REKKEVIK HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 912460894. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 800,000, divided into 1000 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 −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 10.3m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns REKKEVIK HOLDING AS?

BJØRN HENRY ANDERSEN
REKKEVIK HOLDING AS
NOK 0 rev. · NOK −6,000 profit

REKKEVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REKKEVIK HOLDING AS own?

REKKEVIK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REKKEVIK HOLDING AS

Who owns REKKEVIK HOLDING AS?

BJØRN HENRY ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of REKKEVIK HOLDING AS?

REKKEVIK HOLDING AS had revenue of NOK 0 in 2025.

Where is REKKEVIK HOLDING AS based?

REKKEVIK HOLDING AS has its business address in Larvik.

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.