BIZTRAC BETA
Rental and operating of own or leased real estate

BERGEN BYGG AS

Org. no. 968058142 Limited company (AS) Bergen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 20.5m
Operating profit NOK 5.4m
Equity NOK 15.2m
Incorporated 1993
Employees 9
Share capital NOK 100,000

BERGEN BYGG AS is registered as a limited company in Bergen, Vestland with organisation number 968058142. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg/utleie av fast eiendom samt ha interesser i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.5m in revenue and NOK 5.4m in operating profit.

Key figures · 2024

Revenue
NOK 20.5m
Operating profit
NOK 5.4m
Equity
NOK 15.2m
Est. value
NOK 19.7m

Financial health · 2024

Liquidity
2.16
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.1%
Not satisfactory
Equity as a share of total capital

Who owns BERGEN BYGG AS?

JW INVEST AS
BERGEN BYGG AS
NOK 20.5m rev. · NOK 5.4m profit

BERGEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGEN BYGG AS own?

BERGEN BYGG AS holds stakes in 19 companies:

See the full ownership structure →

Frequently asked questions about BERGEN BYGG AS

Who owns BERGEN BYGG AS?

JW INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN BYGG AS?

BERGEN BYGG AS had revenue of NOK 20.5m in 2024.

Who is the general manager of BERGEN BYGG AS?

Jan Willy Rasmussen is registered as general manager of BERGEN BYGG AS.

Where is BERGEN BYGG AS based?

BERGEN 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.