BIZTRAC BETA
Construction of residential and non-residential buildings

TIMBERBYGG AS

Org. no. 922577021 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 96.8m
Operating profit NOK 5.0m
Equity NOK 8.0m
Incorporated 2019
Employees 41
Share capital NOK 40,000

TIMBERBYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922577021. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019 and has 41 registered employees. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Å drive entrepriser innenfor tradisjonell byggmester og entreprenørvirksomhet, samt alt som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 96.8m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 96.8m
Operating profit
NOK 5.0m
Equity
NOK 8.0m
Est. value
NOK 20.2m

Financial health · 2024

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.0%
Good
Equity as a share of total capital

Who owns TIMBERBYGG AS?

TIMBERBYGG HOLDING AS
TIMBERBYGG AS
NOK 96.8m rev. · NOK 5.0m profit

TIMBERBYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TIMBERBYGG AS er morselskap for 2 datterselskaper:

Frequently asked questions about TIMBERBYGG AS

Who owns TIMBERBYGG AS?

TIMBERBYGG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TIMBERBYGG AS?

TIMBERBYGG AS had revenue of NOK 96.8m in 2024.

Who is the general manager of TIMBERBYGG AS?

Anders Græsli Øiaas is registered as general manager of TIMBERBYGG AS.

Where is TIMBERBYGG AS based?

TIMBERBYGG AS has its business address in Ranheim.

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.