BIZTRAC BETA
Other captive investment companies

BORGESEN HOLDING AS

Org. no. 919184604 Limited company (AS) Malvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 1.2m
Incorporated 2017
Share capital NOK 35,000

Signals

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

BORGESEN HOLDING AS is registered as a limited company in Malvik, Trøndelag with organisation number 919184604. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 35,000, divided into 17742 shares. The company's stated purpose is: “Å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 1.2m
Est. value
NOK 953,000

Financial health · 2025

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

Who owns BORGESEN HOLDING AS?

JØRGEN FRENKEN BORGESEN
BORGESEN HOLDING AS
NOK 0 rev. · NOK −24,000 profit

BORGESEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BORGESEN HOLDING AS own?

BORGESEN HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

BORGESEN HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about BORGESEN HOLDING AS

Who owns BORGESEN HOLDING AS?

JØRGEN FRENKEN BORGESEN is the largest registered owner, with 100.0%.

What is the revenue of BORGESEN HOLDING AS?

BORGESEN HOLDING AS had revenue of NOK 0 in 2025.

Where is BORGESEN HOLDING AS based?

BORGESEN HOLDING AS has its business address in Saksvik.

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.