BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

THORESEN ANLEGG OG TRANSPORT AS

Org. no. 987164042 Limited company (AS) Sarpsborg Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 17,000
Equity NOK 810,000
Incorporated 2004
Share capital NOK 300,000

THORESEN ANLEGG OG TRANSPORT AS is registered as a limited company in Sarpsborg, Østfold with organisation number 987164042. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2004. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Transport på anlegg, stenlegging, container transport, container utleie, salg av møle, bark og jordforbedringsprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 17,000
Equity
NOK 810,000
Est. value
NOK 439,000

Financial health · 2024

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.6%
Satisfactory
Equity as a share of total capital

Who owns THORESEN ANLEGG OG TRANSPORT AS?

RAYMOND NICOLAYSEN HOLDING AS
THORESEN ANLEGG OG TRANSPORT AS
NOK 8.9m rev. · NOK 17,000 profit

THORESEN ANLEGG OG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THORESEN ANLEGG OG TRANSPORT AS

Who owns THORESEN ANLEGG OG TRANSPORT AS?

RAYMOND NICOLAYSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of THORESEN ANLEGG OG TRANSPORT AS?

THORESEN ANLEGG OG TRANSPORT AS had revenue of NOK 8.9m in 2024.

Where is THORESEN ANLEGG OG TRANSPORT AS based?

THORESEN ANLEGG OG TRANSPORT AS has its business address in Yven.

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.