BIZTRAC BETA
Freight transport by road

Ø. ERIKSEN TRANSPORT AS

Org. no. 992838019 Limited company (AS) Søndre Land Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 21.6m
Operating profit NOK 686,000
Equity NOK 7.7m
Incorporated 2008
Employees 33
Share capital NOK 400,000

Ø. ERIKSEN TRANSPORT AS is registered as a limited company in Søndre Land, Innlandet with organisation number 992838019. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2008 and has 33 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Utførelse av transporttjenester og alt som står i forbindelse med dette, samt investering og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.6m in revenue and NOK 686,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.6m
Operating profit
NOK 686,000
Equity
NOK 7.7m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns Ø. ERIKSEN TRANSPORT AS?

ØYSTEIN ERIKSEN
Ø. ERIKSEN TRANSPORT AS
NOK 21.6m rev. · NOK 686,000 profit

Ø. ERIKSEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Ø. ERIKSEN TRANSPORT AS

Who owns Ø. ERIKSEN TRANSPORT AS?

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

What is the revenue of Ø. ERIKSEN TRANSPORT AS?

Ø. ERIKSEN TRANSPORT AS had revenue of NOK 21.6m in 2024.

Who is the general manager of Ø. ERIKSEN TRANSPORT AS?

Øystein Eriksen is registered as general manager of Ø. ERIKSEN TRANSPORT AS.

Where is Ø. ERIKSEN TRANSPORT AS based?

Ø. ERIKSEN TRANSPORT AS has its business address in Fall.

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.