BIZTRAC BETA
Wholesale of other machinery and equipment

BRO KOMPETANSE AS

Org. no. 925100102 Limited company (AS) Sandefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 645,000
Operating profit NOK −318,000
Equity NOK 486,000
Incorporated 2020
Share capital NOK 60,000

Signals

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

BRO KOMPETANSE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 925100102. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Tjenesteyting, konsulentvirksomhet innen "Management For Hire", rekruttering. Samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 645,000 in revenue and NOK −318,000 in operating profit.

Key figures · 2024

Revenue
NOK 645,000
Operating profit
NOK −318,000
Equity
NOK 486,000
Est. value
NOK 607,000

Financial health · 2024

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

Who owns BRO KOMPETANSE AS?

JON BJÅEN
BRO KOMPETANSE AS
NOK 645,000 rev. · NOK −318,000 profit

BRO KOMPETANSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRO KOMPETANSE AS

Who owns BRO KOMPETANSE AS?

JON BJÅEN is the largest registered owner, with 100.0%.

What is the revenue of BRO KOMPETANSE AS?

BRO KOMPETANSE AS had revenue of NOK 645,000 in 2024.

Who is the general manager of BRO KOMPETANSE AS?

Jon Bjåen is registered as general manager of BRO KOMPETANSE AS.

Where is BRO KOMPETANSE AS based?

BRO KOMPETANSE AS has its business address in Sandefjord.

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.