biztrac. BETA
COMPANY REGISTER PROFILE
921749333 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

BØRRES HOLDING AS

Org. no. 921749333 Limited company (AS) Porsgrunn Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −125,000
Equity NOK 19.7m
Incorporated 2018
Share capital NOK 48,000

Signals

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

BØRRES HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 921749333. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 48,000, divided into 1360 shares. The company's stated purpose is: “Investere i finans- og realobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −125,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −125,000
▼ −1175 %
Equity
NOK 19.7m
▲ +762 %
Est. value
NOK 80.7m

Financial health · 2025

Liquidity
12.55
Very good
Current assets ÷ current liabilities
Profitability
162.9%
Very good
Return on total assets
Solidity
93.4%
Very good
Equity as a share of total capital

Who owns BØRRES HOLDING AS?

BØRRES HOLDING AS
NOK 0 rev. · NOK −125,000 profit

BØRRES HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BØRRES HOLDING AS own?

BØRRES HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BØRRES HOLDING AS

Who owns BØRRES HOLDING AS?

Børre Aagesen is the largest registered owner, with 100.0%.

What is the revenue of BØRRES HOLDING AS?

BØRRES HOLDING AS had revenue of NOK 0 in 2025.

Where is BØRRES HOLDING AS based?

BØRRES HOLDING AS has its business address in Porsgrunn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.