BIZTRAC BETA
Freight transport by road

FOSTERVOLL TRANSPORT AS

Org. no. 995101793 Limited company (AS) Sula Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −121,000
Equity NOK 384,000
Incorporated 2010
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−121k kr).

FOSTERVOLL TRANSPORT AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 995101793. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2010. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Transport med lastebil, samt deltagelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −121,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −121,000
Equity
NOK 384,000
Est. value
NOK 960,000

Financial health · 2025

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

Who owns FOSTERVOLL TRANSPORT AS?

ØYSTEIN FOSTERVOLL
FOSTERVOLL TRANSPORT AS
NOK 1.6m rev. · NOK −121,000 profit

FOSTERVOLL TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSTERVOLL TRANSPORT AS

Who owns FOSTERVOLL TRANSPORT AS?

ØYSTEIN FOSTERVOLL is the largest registered owner, with 100.0%.

What is the revenue of FOSTERVOLL TRANSPORT AS?

FOSTERVOLL TRANSPORT AS had revenue of NOK 1.6m in 2025.

Who is the general manager of FOSTERVOLL TRANSPORT AS?

Øystein Fostervoll is registered as general manager of FOSTERVOLL TRANSPORT AS.

Where is FOSTERVOLL TRANSPORT AS based?

FOSTERVOLL TRANSPORT AS has its business address in Mauseidvå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.