BIZTRAC BETA
Uoppgitt

BORRE HOLDING AS

Org. no. 925224383 Limited company (AS) Horten Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 120,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

BORRE HOLDING AS is registered as a limited company in Horten, Vestfold with organisation number 925224383. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og andeler. Kunne gi gaver til veldedige og humanitære organisasjoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 120,000
Est. value
NOK 141,000

Financial health · 2024

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

Who owns BORRE HOLDING AS?

GUNHILD VÅRDAL HØYEM
BORRE HOLDING AS
NOK 0 rev. · NOK −16,000 profit

BORRE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BORRE HOLDING AS own?

BORRE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BORRE HOLDING AS

Who owns BORRE HOLDING AS?

GUNHILD VÅRDAL HØYEM is the largest registered owner, with 100.0%.

What is the revenue of BORRE HOLDING AS?

BORRE HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of BORRE HOLDING AS?

Gunhild Vårdal Høyem is registered as general manager of BORRE HOLDING AS.

Where is BORRE HOLDING AS based?

BORRE HOLDING AS has its business address in Borre.

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.