BIZTRAC BETA
Other technical consultancy

PIPECONNECTOR AS

Org. no. 913664868 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −43,000
Equity NOK −873,000
Incorporated 2014
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−873k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).

PIPECONNECTOR AS is registered as a limited company in Bærum, Akershus with organisation number 913664868. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er knyttet til utvikling, produksjon og kommersialisering av undervannsutstyr relatert til produksjon av olje og gass og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −43,000
Equity
NOK −873,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PIPECONNECTOR AS?

TOOL TECH AS
PIPECONNECTOR AS
· NOK −43,000 profit

PIPECONNECTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIPECONNECTOR AS

Who owns PIPECONNECTOR AS?

TOOL TECH AS is the largest registered owner, with 100.0%.

Who is the general manager of PIPECONNECTOR AS?

Magne Rød is registered as general manager of PIPECONNECTOR AS.

Where is PIPECONNECTOR AS based?

PIPECONNECTOR AS has its business address in Rykkinn.

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.