BIZTRAC BETA
Site preparation

VASSBAKK & STOL AS

Org. no. 927048841 Limited company (AS) Karmøy Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 3.2bn
Operating profit NOK 201.8m
Equity NOK 281.0m
Incorporated 1976
Employees 759
Share capital NOK 360,000

VASSBAKK & STOL AS is registered as a limited company in Karmøy, Rogaland with organisation number 927048841. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1976 and has 759 registered employees. Registered share capital is NOK 360,000. The company's stated purpose is: “Entreprenørvirksomhet og alt som dermed står i forbindelse. Selskapet skal kunne erverve og drive fast eiendom og skal kunne delta i stiftelsen av, og eie andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2bn in revenue and NOK 201.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.2bn
Operating profit
NOK 201.8m
Equity
NOK 281.0m
Est. value
NOK 808.6m

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.0%
Good
Equity as a share of total capital

Who owns VASSBAKK & STOL AS?

SKANSKA NORGE AS
VASSBAKK & STOL AS
NOK 3.2bn rev. · NOK 201.8m profit

VASSBAKK & STOL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VASSBAKK & STOL AS er morselskap for 11 datterselskaper:

Frequently asked questions about VASSBAKK & STOL AS

Who owns VASSBAKK & STOL AS?

SKANSKA NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of VASSBAKK & STOL AS?

VASSBAKK & STOL AS had revenue of NOK 3.2bn in 2025.

Who is the general manager of VASSBAKK & STOL AS?

Richard Kvalevaag is registered as general manager of VASSBAKK & STOL AS.

Where is VASSBAKK & STOL AS based?

VASSBAKK & STOL AS has its business address in Kopervik.

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.