BIZTRAC BETA
Joinery installation

STOKKE BYGG AS

Org. no. 996226824 Limited company (AS) Sandefjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 112.7m
Operating profit NOK 5.2m
Equity NOK 26.3m
Incorporated 2010
Employees 38
Share capital NOK 1.0m

STOKKE BYGG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 996226824. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2010 and has 38 registered employees. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet herunder tømrerarbeid, murerarbeid og hva hertil står i forbindelse. Selskapet skal også kunne bedrive handel, investeringsvirksomhet og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 112.7m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 112.7m
Operating profit
NOK 5.2m
Equity
NOK 26.3m
Est. value
NOK 30.1m

Financial health · 2024

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

Who owns STOKKE BYGG AS?

ROAR HIDLE HOLDING AS
STOKKE BYGG AS
NOK 112.7m rev. · NOK 5.2m profit

STOKKE BYGG AS has 4 registered shareholders:

All shareholders and roles →

Group structure

STOKKE BYGG AS er morselskap for 2 datterselskaper:

Frequently asked questions about STOKKE BYGG AS

Who owns STOKKE BYGG AS?

ROAR HIDLE HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of STOKKE BYGG AS?

STOKKE BYGG AS had revenue of NOK 112.7m in 2024.

Who is the general manager of STOKKE BYGG AS?

Roar Hidle is registered as general manager of STOKKE BYGG AS.

Where is STOKKE BYGG AS based?

STOKKE BYGG AS has its business address in Stokke.

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.