BIZTRAC BETA
Other captive investment companies

BXO INVEST AS

Org. no. 913911229 Limited company (AS) Hyllestad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 657,000
Incorporated 2014
Share capital NOK 250,000

Signals

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

BXO INVEST AS is registered as a limited company in Hyllestad, Vestland with organisation number 913911229. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 250,000, divided into 2500 shares. The company's stated purpose is: “Investering i aksjar, verdipapir, fast eigedom samt anna tilknytta verksemd.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 657,000
Est. value
NOK 600,000

Financial health · 2024

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

Who owns BXO INVEST AS?

TORE BRÅSTAD
BXO INVEST AS
NOK 0 rev. · NOK −13,000 profit

BXO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BXO INVEST AS own?

BXO INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BXO INVEST AS

Who owns BXO INVEST AS?

TORE BRÅSTAD is the largest registered owner, with 100.0%.

What is the revenue of BXO INVEST AS?

BXO INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of BXO INVEST AS?

Tore Bråstad is registered as general manager of BXO INVEST AS.

Where is BXO INVEST AS based?

BXO INVEST AS has its business address in Leirvik I Sogn.

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.