biztrac. BETA
COMPANY REGISTER PROFILE
924596082 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BRAKET HOLDING AS

Org. no. 924596082 Limited company (AS) Krødsherad Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 707,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

BRAKET HOLDING AS is registered as a limited company in Krødsherad, Buskerud with organisation number 924596082. 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 andre selskaper. Eie, kjøpe og selge aksjer, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▼ −15 %
Equity
NOK 707,000
▲ +19 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
39.9%
Good
Equity as a share of total capital

Who owns BRAKET HOLDING AS?

BRAKET HOLDING AS
NOK 0 rev. · NOK −9,000 profit

BRAKET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRAKET HOLDING AS own?

BRAKET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRAKET HOLDING AS

Who owns BRAKET HOLDING AS?

Espen Andre Holte is the largest registered owner, with 100.0%.

What is the revenue of BRAKET HOLDING AS?

BRAKET HOLDING AS had revenue of NOK 0 in 2025.

Where is BRAKET HOLDING AS based?

BRAKET HOLDING AS has its business address in Noresund.

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.