BIZTRAC BETA
Uoppgitt

A. SKARSTEIN HOLDING AS

Org. no. 928328651 Limited company (AS) Lier Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −933,000
Equity NOK 3.4m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−933k kr).

A. SKARSTEIN HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 928328651. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i aksjer og andre finansielle instrumenter, deltakelse i andre selskaper og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −933,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −933,000
Equity
NOK 3.4m
Est. value
NOK 28.1m

Financial health · 2025

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

Who owns A. SKARSTEIN HOLDING AS?

ANDERS GUTTORMSON SKARSTEIN
A. SKARSTEIN HOLDING AS
NOK 0 rev. · NOK −933,000 profit

A. SKARSTEIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A. SKARSTEIN HOLDING AS own?

A. SKARSTEIN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about A. SKARSTEIN HOLDING AS

Who owns A. SKARSTEIN HOLDING AS?

ANDERS GUTTORMSON SKARSTEIN is the largest registered owner, with 100.0%.

What is the revenue of A. SKARSTEIN HOLDING AS?

A. SKARSTEIN HOLDING AS had revenue of NOK 0 in 2025.

Where is A. SKARSTEIN HOLDING AS based?

A. SKARSTEIN HOLDING AS has its business address in Lierskogen.

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.