BIZTRAC BETA
Other technical consultancy

BRABO II AS

Org. no. 894280212 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −147,000
Equity NOK 437,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

BRABO II AS is registered as a limited company in Oslo, Oslo with organisation number 894280212. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Framstilling/salg av analyser, investeringer og andre produkter som naturlig faller sammen med dette herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −147,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −147,000
Equity
NOK 437,000
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns BRABO II AS?

BJØRN BJØRNSSON HOLTA
BRABO II AS
NOK 0 rev. · NOK −147,000 profit

BRABO II AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRABO II AS own?

BRABO II AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BRABO II AS

Who owns BRABO II AS?

BJØRN BJØRNSSON HOLTA is the largest registered owner, with 60.0%.

What is the revenue of BRABO II AS?

BRABO II AS had revenue of NOK 0 in 2024.

Where is BRABO II AS based?

BRABO II AS has its business address in Oslo.

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.