biztrac. BETA
COMPANY REGISTER PROFILE
987727365 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

EURO TRANSPORT AS

Org. no. 987727365 Limited company (AS) Lørenskog Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 22.6m
Operating profit NOK 1.4m
Equity NOK 6.5m
Incorporated 2004
Employees 20
Share capital NOK 800,000

EURO TRANSPORT AS is registered as a limited company in Lørenskog, Akershus with organisation number 987727365. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2004 and has 20 registered employees. Registered share capital is NOK 800,000, divided into 200 shares. The company's stated purpose is: “Godstransport på vei, innland og utland, logistikk, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.6m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 22.6m
▲ +30 %
Operating profit
NOK 1.4m
▲ +107 %
Equity
NOK 6.5m
▲ +10 %
Est. value
NOK 8.2m

Financial health · 2025

Liquidity
2.23
Very good
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
54.3%
Very good
Equity as a share of total capital

Who owns EURO TRANSPORT AS?

EURO TRANSPORT AS
NOK 22.6m rev. · NOK 1.4m profit

EURO TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EURO TRANSPORT AS

Who owns EURO TRANSPORT AS?

Thayaparan Sivalingam is the largest registered owner, with 100.0%.

What is the revenue of EURO TRANSPORT AS?

EURO TRANSPORT AS had revenue of NOK 22.6m in 2025.

Who is the general manager of EURO TRANSPORT AS?

Thayaparan Sivalingam is registered as general manager of EURO TRANSPORT AS.

Where is EURO TRANSPORT AS based?

EURO TRANSPORT AS has its business address in Lørenskog.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.