BIZTRAC BETA
Rental and operating of own or leased real estate

TRE BRØR AS

Org. no. 993324337 Limited company (AS) Voss Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −1.5m
Equity NOK −5.9m
Incorporated 2008
Employees 5
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

TRE BRØR AS is registered as a limited company in Voss, Vestland with organisation number 993324337. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av fast eiendom og serveringsvirksomhet”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −1.5m
Equity
NOK −5.9m

Financial health · 2024

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

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

Who owns TRE BRØR AS?

BJØRN BRUNBORG AS
TRE BRØR AS
NOK 1.4m rev. · NOK −1.5m profit

TRE BRØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRE BRØR AS

Who owns TRE BRØR AS?

BJØRN BRUNBORG AS is the largest registered owner, with 100.0%.

What is the revenue of TRE BRØR AS?

TRE BRØR AS had revenue of NOK 1.4m in 2024.

Who is the general manager of TRE BRØR AS?

Bjørn Helge Brunborg is registered as general manager of TRE BRØR AS.

Where is TRE BRØR AS based?

TRE BRØR AS has its business address in Voss.

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.