BIZTRAC BETA
Other captive investment companies

HAVSODDEN INVEST AS

Org. no. 921493983 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 585,000
Operating profit NOK 571,000
Equity NOK 2.0m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

HAVSODDEN INVEST AS is registered as a limited company in Arendal, Agder with organisation number 921493983. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 585,000 in revenue and NOK 571,000 in operating profit.

Key figures · 2025

Revenue
NOK 585,000
Operating profit
NOK 571,000
Equity
NOK 2.0m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns HAVSODDEN INVEST AS?

FREDRIK BOTHA
HAVSODDEN INVEST AS
NOK 585,000 rev. · NOK 571,000 profit

HAVSODDEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAVSODDEN INVEST AS own?

HAVSODDEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAVSODDEN INVEST AS

Who owns HAVSODDEN INVEST AS?

FREDRIK BOTHA is the largest registered owner, with 100.0%.

What is the revenue of HAVSODDEN INVEST AS?

HAVSODDEN INVEST AS had revenue of NOK 585,000 in 2025.

Where is HAVSODDEN INVEST AS based?

HAVSODDEN INVEST AS has its business address in Kolbjørnsvik.

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.