BIZTRAC BETA
Construction of residential and non-residential buildings

PRO-BYGG AS

Org. no. 888192832 Limited company (AS) Tjeldsund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −45,000
Equity NOK 513,000
Incorporated 2005
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−45k kr).

PRO-BYGG AS is registered as a limited company in Tjeldsund, Troms with organisation number 888192832. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygninger, snekkervirksomhet, entreprenørvirksomhet samt kunne delta i annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −45,000
Equity
NOK 513,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.5%
Very good
Equity as a share of total capital

Who owns PRO-BYGG AS?

JAN ARNE ROSENHAUG
PRO-BYGG AS
NOK 4.2m rev. · NOK −45,000 profit

PRO-BYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRO-BYGG AS

Who owns PRO-BYGG AS?

JAN ARNE ROSENHAUG is the largest registered owner, with 34.0%.

What is the revenue of PRO-BYGG AS?

PRO-BYGG AS had revenue of NOK 4.2m in 2025.

Who is the general manager of PRO-BYGG AS?

Håvard Arne Vesterheim is registered as general manager of PRO-BYGG AS.

Where is PRO-BYGG AS based?

PRO-BYGG AS has its business address in Evenskjer.

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.