BIZTRAC BETA
Uoppgitt

STALSBERG HOLDING AS

Org. no. 934140710 Limited company (AS) Eidsvoll Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 20,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

STALSBERG HOLDING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 934140710. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 20,000
Est. value
NOK 24,000

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.0%
Weak
Equity as a share of total capital

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

Who owns STALSBERG HOLDING AS?

HENNING STALSBERG
STALSBERG HOLDING AS
· NOK −5,000 profit

STALSBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STALSBERG HOLDING AS own?

STALSBERG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STALSBERG HOLDING AS

Who owns STALSBERG HOLDING AS?

HENNING STALSBERG is the largest registered owner, with 100.0%.

Who is the general manager of STALSBERG HOLDING AS?

Henning Stalsberg is registered as general manager of STALSBERG HOLDING AS.

Where is STALSBERG HOLDING AS based?

STALSBERG HOLDING AS has its business address in Dal.

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.