BIZTRAC BETA
Construction of residential and non-residential buildings

CONTA BYGG AS

Org. no. 921726589 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK −410,000
Equity NOK 29,000
Incorporated 2018
Employees 12
Share capital NOK 30,000

Signals

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

CONTA BYGG AS is registered as a limited company in Bergen, Vestland with organisation number 921726589. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Virksomhet innen bygg og anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK −410,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK −410,000
Equity
NOK 29,000
Est. value
NOK 948,000

Financial health · 2024

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

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

Who owns CONTA BYGG AS?

TORE ANDRE BERLAND
CONTA BYGG AS
NOK 2.7m rev. · NOK −410,000 profit

CONTA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CONTA BYGG AS

Who owns CONTA BYGG AS?

TORE ANDRE BERLAND is the largest registered owner, with 100.0%.

What is the revenue of CONTA BYGG AS?

CONTA BYGG AS had revenue of NOK 2.7m in 2024.

Who is the general manager of CONTA BYGG AS?

Tore Andre Berland is registered as general manager of CONTA BYGG AS.

Where is CONTA BYGG AS based?

CONTA BYGG AS has its business address in Bergen.

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.