biztrac. BETA
COMPANY REGISTER PROFILE
956791456 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TRYSILBYGG AS

Org. no. 956791456 Limited company (AS) Drammen Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 638.9m
Operating profit NOK 18.8m
Equity NOK 61.9m
Incorporated 1990
Employees 94
Share capital NOK 336,000

TRYSILBYGG AS is registered as a limited company in Drammen, Buskerud with organisation number 956791456. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1990 and has 94 registered employees. Registered share capital is NOK 336,000, divided into 3356201 shares. The company's stated purpose is: “Handel, entreprenør- og finansieringsvirksomhet samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 638.9m in revenue and NOK 18.8m in operating profit.

Key figures · 2025

Revenue
NOK 638.9m
▼ −3 %
Operating profit
NOK 18.8m
▲ +10723 %
Equity
NOK 61.9m
▼ −7 %
Est. value
NOK 65.2m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
28.0%
Good
Equity as a share of total capital

Who owns TRYSILBYGG AS?

TRYSILBYGG AS
NOK 638.9m rev. · NOK 18.8m profit

TRYSILBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYSILBYGG AS

Who owns TRYSILBYGG AS?

TRYSILHUSGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of TRYSILBYGG AS?

TRYSILBYGG AS had revenue of NOK 638.9m in 2025.

Who is the general manager of TRYSILBYGG AS?

Arve Gunnestad is registered as general manager of TRYSILBYGG AS.

Where is TRYSILBYGG AS based?

TRYSILBYGG AS has its business address in Drammen.

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.