BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRN BREIEN AS

Org. no. 888984542 Limited company (AS) Hvaler Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −74,000
Equity NOK −4.6m
Incorporated 2005
Share capital NOK 2.6m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−74k kr).

BJØRN BREIEN AS is registered as a limited company in Hvaler, Østfold with organisation number 888984542. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.6m, divided into 2600 shares. The company's stated purpose is: “Investeringsselskap, ved eie, kjøp og salg av aksjer og fast eiendom, forvalte aksjer og andeler i andre selskap, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −74,000
Equity
NOK −4.6m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJØRN BREIEN AS?

THOR REINHOLT BREIEN
BJØRN BREIEN AS
· NOK −74,000 profit

BJØRN BREIEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRN BREIEN AS own?

BJØRN BREIEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRN BREIEN AS

Who owns BJØRN BREIEN AS?

THOR REINHOLT BREIEN is the largest registered owner, with 100.0%.

Who is the general manager of BJØRN BREIEN AS?

Thor Reinholt Breien is registered as general manager of BJØRN BREIEN AS.

Where is BJØRN BREIEN AS based?

BJØRN BREIEN AS has its business address in Vesterøy.

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.