BIZTRAC BETA
Other captive investment companies

BØRKE HOLDING AS

Org. no. 988938955 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −77,000
Equity NOK 200,000
Incorporated 2005
Share capital NOK 200,000

Signals

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

BØRKE HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 988938955. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå handels-, agentur-, konsulent-, eksport-, import-, investerings- og næringsvirksomhet av enhver art, herunder investering i fast eiendom, verdipapirer og utlån, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −77,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −77,000
Equity
NOK 200,000
Est. value
NOK 183,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.7%
Weak
Equity as a share of total capital

Who owns BØRKE HOLDING AS?

KNUT BØRKE
BØRKE HOLDING AS
NOK 0 rev. · NOK −77,000 profit

BØRKE HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØRKE HOLDING AS

Who owns BØRKE HOLDING AS?

KNUT BØRKE is the largest registered owner, with 68.0%.

What is the revenue of BØRKE HOLDING AS?

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

Where is BØRKE HOLDING AS based?

BØRKE HOLDING AS has its business address in Drøbak.

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.