BIZTRAC BETA
Cutting, shaping and finishing of stone

STRANDBERG UTEMILJØ AS

Org. no. 927160412 Limited company (AS) Larvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK −407,000
Equity NOK −289,000
Incorporated 2021
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−289k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−407k kr).

STRANDBERG UTEMILJØ AS is registered as a limited company in Larvik, Vestfold with organisation number 927160412. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av ulike steinprodukter, med hovedfokus på utomhusanlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK −407,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK −407,000
Equity
NOK −289,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STRANDBERG UTEMILJØ AS?

KLEPAKER HOLDING AS
STRANDBERG UTEMILJØ AS
NOK 5.4m rev. · NOK −407,000 profit

STRANDBERG UTEMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDBERG UTEMILJØ AS

Who owns STRANDBERG UTEMILJØ AS?

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

What is the revenue of STRANDBERG UTEMILJØ AS?

STRANDBERG UTEMILJØ AS had revenue of NOK 5.4m in 2024.

Where is STRANDBERG UTEMILJØ AS based?

STRANDBERG UTEMILJØ 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.