BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

BÅSTØ MASKINPARK AS

Org. no. 929980085 Limited company (AS) Hemsedal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 156,000
Operating profit NOK 32,000
Equity NOK 97,000
Incorporated 2022
Share capital NOK 30,000

BÅSTØ MASKINPARK AS is registered as a limited company in Hemsedal, Buskerud with organisation number 929980085. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av maskiner og utstyr til egne bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 156,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 156,000
Operating profit
NOK 32,000
Equity
NOK 97,000
Est. value
NOK 164,000

Financial health · 2025

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

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

Who owns BÅSTØ MASKINPARK AS?

SKOGSHORN HOLD AS
BÅSTØ MASKINPARK AS
NOK 156,000 rev. · NOK 32,000 profit

BÅSTØ MASKINPARK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BÅSTØ MASKINPARK AS

Who owns BÅSTØ MASKINPARK AS?

SKOGSHORN HOLD AS is the largest registered owner, with 50.0%.

What is the revenue of BÅSTØ MASKINPARK AS?

BÅSTØ MASKINPARK AS had revenue of NOK 156,000 in 2025.

Who is the general manager of BÅSTØ MASKINPARK AS?

Torstein Storeskar is registered as general manager of BÅSTØ MASKINPARK AS.

Where is BÅSTØ MASKINPARK AS based?

BÅSTØ MASKINPARK AS has its business address in Hemsedal.

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.