BIZTRAC BETA
Plumbing installation

PIPETEAM AS

Org. no. 832562882 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 36.3m
Operating profit NOK 554,000
Equity NOK 425,000
Incorporated 2023
Employees 50
Share capital NOK 50,000

PIPETEAM AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 832562882. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023 and has 50 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Innrednings -og installasjonsarbeid på skip over 100 br.tonn. Isolasjonsarbeid, gulvstøping, gulvlegging og montering av rør. Herunder salg av varer som hører til under denne virksomheten, samt hva mer som står i forbindelse, herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.3m in revenue and NOK 554,000 in operating profit.

Key figures · 2024

Revenue
NOK 36.3m
Operating profit
NOK 554,000
Equity
NOK 425,000
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns PIPETEAM AS?

PER JOHANSEN
PIPETEAM AS
NOK 36.3m rev. · NOK 554,000 profit

PIPETEAM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PIPETEAM AS

Who owns PIPETEAM AS?

PER JOHANSEN is the largest registered owner, with 50.0%.

What is the revenue of PIPETEAM AS?

PIPETEAM AS had revenue of NOK 36.3m in 2024.

Who is the general manager of PIPETEAM AS?

Øyvind Dannevig is registered as general manager of PIPETEAM AS.

Where is PIPETEAM AS based?

PIPETEAM AS has its business address in Surnadal.

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.