BIZTRAC BETA
Construction of residential and non-residential buildings

BYGG BRU AS

Org. no. 998578787 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −93,000
Equity NOK 211,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

BYGG BRU AS is registered as a limited company in Asker, Akershus with organisation number 998578787. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av arbeidskraft, tømrertjenester, byggetjenester, produksjon og salgsvirksomhet, agentur, handel samt å interessere seg i andre foretak og hva dermed står i interesse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −93,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −93,000
Equity
NOK 211,000
Est. value
NOK 463,000

Financial health · 2024

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

Who owns BYGG BRU AS?

ROAR OLSEN BRU
BYGG BRU AS
NOK 1.1m rev. · NOK −93,000 profit

BYGG BRU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGG BRU AS

Who owns BYGG BRU AS?

ROAR OLSEN BRU is the largest registered owner, with 100.0%.

What is the revenue of BYGG BRU AS?

BYGG BRU AS had revenue of NOK 1.1m in 2024.

Who is the general manager of BYGG BRU AS?

Roar Olsen Bru is registered as general manager of BYGG BRU AS.

Where is BYGG BRU AS based?

BYGG BRU AS has its business address in Tofte.

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.