BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

DALSJØ RØR & TRANSPORT AS

Org. no. 912227405 Limited company (AS) Eidskog Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 9,000
Equity NOK 379,000
Incorporated 2013
Share capital NOK 30,000

DALSJØ RØR & TRANSPORT AS is registered as a limited company in Eidskog, Innlandet with organisation number 912227405. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøpe å selge produkter til Vei og Anlegg. Selskapet skal også tilby transporttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 9,000
Equity
NOK 379,000
Est. value
NOK 211,000

Financial health · 2024

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

Who owns DALSJØ RØR & TRANSPORT AS?

STEN ERIK DALSJØ
DALSJØ RØR & TRANSPORT AS
NOK 1.8m rev. · NOK 9,000 profit

DALSJØ RØR & TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DALSJØ RØR & TRANSPORT AS

Who owns DALSJØ RØR & TRANSPORT AS?

STEN ERIK DALSJØ is the largest registered owner, with 100.0%.

What is the revenue of DALSJØ RØR & TRANSPORT AS?

DALSJØ RØR & TRANSPORT AS had revenue of NOK 1.8m in 2024.

Who is the general manager of DALSJØ RØR & TRANSPORT AS?

Sten Erik Dalsjø is registered as general manager of DALSJØ RØR & TRANSPORT AS.

Where is DALSJØ RØR & TRANSPORT AS based?

DALSJØ RØR & TRANSPORT AS has its business address in Skotterud.

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.