BIZTRAC BETA
Freight transport by road

VIGGO STIEN TRANSPORT AS

Org. no. 991457224 Limited company (AS) Hemnes Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 9.2m
Operating profit NOK 3.0m
Equity NOK 6.9m
Incorporated 2007
Share capital NOK 100,000

VIGGO STIEN TRANSPORT AS is registered as a limited company in Hemnes, Nordland with organisation number 991457224. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snøbrøyting, tippkjøring samt andre transportoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.2m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 9.2m
Operating profit
NOK 3.0m
Equity
NOK 6.9m
Est. value
NOK 13.0m

Financial health · 2025

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

Who owns VIGGO STIEN TRANSPORT AS?

VIGGO STIEN
VIGGO STIEN TRANSPORT AS
NOK 9.2m rev. · NOK 3.0m profit

VIGGO STIEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIGGO STIEN TRANSPORT AS own?

VIGGO STIEN TRANSPORT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIGGO STIEN TRANSPORT AS

Who owns VIGGO STIEN TRANSPORT AS?

VIGGO STIEN is the largest registered owner, with 100.0%.

What is the revenue of VIGGO STIEN TRANSPORT AS?

VIGGO STIEN TRANSPORT AS had revenue of NOK 9.2m in 2025.

Who is the general manager of VIGGO STIEN TRANSPORT AS?

Viggo Stien is registered as general manager of VIGGO STIEN TRANSPORT AS.

Where is VIGGO STIEN TRANSPORT AS based?

VIGGO STIEN TRANSPORT AS has its business address in Bjerka.

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.