BIZTRAC BETA
Freight transport by road

SVEIN HAUGEN TRANSPORT AS

Org. no. 976466748 Limited company (AS) Larvik Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 14.5m
Operating profit NOK 39,000
Equity NOK 2.0m
Incorporated 1996
Employees 8
Share capital NOK 100,000

SVEIN HAUGEN TRANSPORT AS is registered as a limited company in Larvik, Vestfold with organisation number 976466748. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1996 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportforretning samt hva hermed står i forbindelse, også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.5m in revenue and NOK 39,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.5m
Operating profit
NOK 39,000
Equity
NOK 2.0m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SVEIN HAUGEN TRANSPORT AS?

SIMON E. HAUGEN TRANSPORT AS
SVEIN HAUGEN TRANSPORT AS
NOK 14.5m rev. · NOK 39,000 profit

SVEIN HAUGEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVEIN HAUGEN TRANSPORT AS

Who owns SVEIN HAUGEN TRANSPORT AS?

SIMON E. HAUGEN TRANSPORT AS is the largest registered owner, with 90.0%.

What is the revenue of SVEIN HAUGEN TRANSPORT AS?

SVEIN HAUGEN TRANSPORT AS had revenue of NOK 14.5m in 2025.

Who is the general manager of SVEIN HAUGEN TRANSPORT AS?

Svein Eilev Haugen is registered as general manager of SVEIN HAUGEN TRANSPORT AS.

Where is SVEIN HAUGEN TRANSPORT AS based?

SVEIN HAUGEN TRANSPORT AS has its business address in Larvik.

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.