BIZTRAC BETA
Freight transport by road

VOSS MASKINTRANSPORT AS

Org. no. 926523481 Limited company (AS) Voss Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 272,000
Operating profit NOK 61,000
Equity NOK 297,000
Incorporated 2021
Share capital NOK 60,000

VOSS MASKINTRANSPORT AS is registered as a limited company in Voss, Vestland with organisation number 926523481. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Gods og varetransport, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 272,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 272,000
Operating profit
NOK 61,000
Equity
NOK 297,000
Est. value
NOK 348,000

Financial health · 2024

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

Who owns VOSS MASKINTRANSPORT AS?

EIRIK BAKKETUN
VOSS MASKINTRANSPORT AS
NOK 272,000 rev. · NOK 61,000 profit

VOSS MASKINTRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOSS MASKINTRANSPORT AS

Who owns VOSS MASKINTRANSPORT AS?

EIRIK BAKKETUN is the largest registered owner, with 50.0%.

What is the revenue of VOSS MASKINTRANSPORT AS?

VOSS MASKINTRANSPORT AS had revenue of NOK 272,000 in 2024.

Who is the general manager of VOSS MASKINTRANSPORT AS?

Eirik Bakketun is registered as general manager of VOSS MASKINTRANSPORT AS.

Where is VOSS MASKINTRANSPORT AS based?

VOSS MASKINTRANSPORT AS has its business address in Skulestadmo.

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.