biztrac. BETA
COMPANY REGISTER PROFILE
986670688 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

BERGEN BYGG SYSTEM AS

Org. no. 986670688 Limited company (AS) Bergen Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 74.8m
Operating profit NOK 3.8m
Equity NOK 1.6m
Incorporated 2004
Employees 25
Share capital NOK 100,000

BERGEN BYGG SYSTEM AS is registered as a limited company in Bergen, Vestland with organisation number 986670688. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2004 and has 25 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre håndverkertjenester og tilhørende virksomhet, eie og forvalte eiendommer samt ved aksjekjøp å interessere seg i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.8m in revenue and NOK 3.8m in operating profit.

Key figures · 2025

Revenue
NOK 74.8m
▲ +14 %
Operating profit
NOK 3.8m
▲ +288 %
Equity
NOK 1.6m
▼ −57 %
Est. value
NOK 11.5m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
24.4%
Very good
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns BERGEN BYGG SYSTEM AS?

BERGEN BYGG SYSTEM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGEN BYGG SYSTEM AS

Who owns BERGEN BYGG SYSTEM AS?

JOA GRUPPEN AS is the largest registered owner, with 50.0%.

What is the revenue of BERGEN BYGG SYSTEM AS?

BERGEN BYGG SYSTEM AS had revenue of NOK 74.8m in 2025.

Who is the general manager of BERGEN BYGG SYSTEM AS?

Ronny Grahl is registered as general manager of BERGEN BYGG SYSTEM AS.

Where is BERGEN BYGG SYSTEM AS based?

BERGEN BYGG SYSTEM AS has its business address in Nyborg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.