BIZTRAC BETA
Uoppgitt

RONNY SMEDSMO HOLDING AS

Org. no. 922095787 Limited company (AS) Vågå Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 2,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

RONNY SMEDSMO HOLDING AS is registered as a limited company in Vågå, Innlandet with organisation number 922095787. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og det som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 2,000
Est. value
NOK 2,000

Financial health · 2024

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

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

Who owns RONNY SMEDSMO HOLDING AS?

RONNY OVE SMEDSMO
RONNY SMEDSMO HOLDING AS
NOK 0 rev. · NOK −6,000 profit

RONNY SMEDSMO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RONNY SMEDSMO HOLDING AS own?

RONNY SMEDSMO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RONNY SMEDSMO HOLDING AS

Who owns RONNY SMEDSMO HOLDING AS?

RONNY OVE SMEDSMO is the largest registered owner, with 100.0%.

What is the revenue of RONNY SMEDSMO HOLDING AS?

RONNY SMEDSMO HOLDING AS had revenue of NOK 0 in 2024.

Where is RONNY SMEDSMO HOLDING AS based?

RONNY SMEDSMO HOLDING AS has its business address in Vågå.

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.