BIZTRAC BETA
Other technical consultancy

SCANPIPE ENGINEERING AS

Org. no. 925342149 Limited company (AS) Oslo Incorporated 1973 Active
Ownership graph ↗
Operating profit NOK −129,000
Equity NOK 35.3m
Incorporated 1973
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−129k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SCANPIPE ENGINEERING AS is registered as a limited company in Oslo, Oslo with organisation number 925342149. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1973. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Teknisk konsulentvirksomhet og hva dermed står i forbindelse, agenturvirksomhet, samt ved aksje- kjøp, lån og på annen måte å delta i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −129,000
Equity
NOK 35.3m
Est. value
NOK 23.6m

Financial health · 2024

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

Who owns SCANPIPE ENGINEERING AS?

BRICKWALL AS
SCANPIPE ENGINEERING AS
· NOK −129,000 profit

SCANPIPE ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SCANPIPE ENGINEERING AS own?

SCANPIPE ENGINEERING AS holds stakes in 10 companies:

See the full ownership structure →

Group structure

SCANPIPE ENGINEERING AS er morselskap for 3 datterselskaper:

Frequently asked questions about SCANPIPE ENGINEERING AS

Who owns SCANPIPE ENGINEERING AS?

BRICKWALL AS is the largest registered owner, with 100.0%.

Where is SCANPIPE ENGINEERING AS based?

SCANPIPE ENGINEERING AS has its business address in Oslo.

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.