BIZTRAC BETA
Other captive investment companies

FIX INVEST AS

Org. no. 829490072 Limited company (AS) Herøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 4.1m
Incorporated 2022
Share capital NOK 100,000

Signals

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

FIX INVEST AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 829490072. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer samt det som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 4.1m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns FIX INVEST AS?

BØRGE MORTEN FIKSDAL
FIX INVEST AS
NOK 0 rev. · NOK −12,000 profit

FIX INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FIX INVEST AS own?

FIX INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about FIX INVEST AS

Who owns FIX INVEST AS?

BØRGE MORTEN FIKSDAL is the largest registered owner, with 30.0%.

What is the revenue of FIX INVEST AS?

FIX INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of FIX INVEST AS?

Vegard Fiksdal is registered as general manager of FIX INVEST AS.

Where is FIX INVEST AS based?

FIX INVEST AS has its business address in Bølandet.

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.