BIZTRAC BETA
Plumbing installation

AGDER RØRFORNYING AS

Org. no. 926578812 Limited company (AS) Kristiansand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 76,000
Equity NOK 3.4m
Incorporated 2021
Share capital NOK 300,000

AGDER RØRFORNYING AS is registered as a limited company in Kristiansand, Agder with organisation number 926578812. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2021. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Rehabilitering av vann og avløpsrør, og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 76,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
Operating profit
NOK 76,000
Equity
NOK 3.4m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns AGDER RØRFORNYING AS?

TOMMAS EKBERG LIEN
AGDER RØRFORNYING AS
NOK 6.6m rev. · NOK 76,000 profit

AGDER RØRFORNYING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AGDER RØRFORNYING AS own?

AGDER RØRFORNYING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AGDER RØRFORNYING AS

Who owns AGDER RØRFORNYING AS?

TOMMAS EKBERG LIEN is the largest registered owner, with 51.0%.

What is the revenue of AGDER RØRFORNYING AS?

AGDER RØRFORNYING AS had revenue of NOK 6.6m in 2025.

Who is the general manager of AGDER RØRFORNYING AS?

Tommas Ekberg Lien is registered as general manager of AGDER RØRFORNYING AS.

Where is AGDER RØRFORNYING AS based?

AGDER RØRFORNYING AS has its business address in Søgne.

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.