BIZTRAC BETA
Cutting, shaping and finishing of stone

STRANDBERG STEIN AS

Org. no. 960197631 Limited company (AS) Larvik Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 24.5m
Operating profit NOK 1.2m
Equity NOK 4.3m
Incorporated 1991
Employees 13
Share capital NOK 1.7m

STRANDBERG STEIN AS is registered as a limited company in Larvik, Vestfold with organisation number 960197631. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 1991 and has 13 registered employees. Registered share capital is NOK 1.7m, divided into 2450 shares. The company's stated purpose is: “Produksjon, handel og markedsføring av steinpro- dukter, og det som står i forbindelse med dette, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 24.5m
Operating profit
NOK 1.2m
Equity
NOK 4.3m
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns STRANDBERG STEIN AS?

KLEPAKER HOLDING AS
STRANDBERG STEIN AS
NOK 24.5m rev. · NOK 1.2m profit

STRANDBERG STEIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDBERG STEIN AS

Who owns STRANDBERG STEIN AS?

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

What is the revenue of STRANDBERG STEIN AS?

STRANDBERG STEIN AS had revenue of NOK 24.5m in 2024.

Who is the general manager of STRANDBERG STEIN AS?

Hans Petter Strandberg is registered as general manager of STRANDBERG STEIN AS.

Where is STRANDBERG STEIN AS based?

STRANDBERG STEIN AS has its business address in Tjodalyng.

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.