BIZTRAC BETA
Retail sale of motor vehicles

VINTERDALEN AS

Org. no. 921486332 Limited company (AS) Kåfjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 29,000
Operating profit NOK −11,000
Equity NOK 38,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

VINTERDALEN AS is registered as a limited company in Kåfjord, Troms with organisation number 921486332. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp og salg av brukte kjøretøy og investering i eiendom og andre foretak, samt annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 29,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 29,000
Operating profit
NOK −11,000
Equity
NOK 38,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns VINTERDALEN AS?

BJØRN-EVEN SALAMONSEN
VINTERDALEN AS
NOK 29,000 rev. · NOK −11,000 profit

VINTERDALEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VINTERDALEN AS own?

VINTERDALEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VINTERDALEN AS

Who owns VINTERDALEN AS?

BJØRN-EVEN SALAMONSEN is the largest registered owner, with 100.0%.

What is the revenue of VINTERDALEN AS?

VINTERDALEN AS had revenue of NOK 29,000 in 2024.

Where is VINTERDALEN AS based?

VINTERDALEN AS has its business address in Olderdalen.

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.