BIZTRAC BETA
Other technical consultancy

PIPE SUPPORT VERIFICATION AS

Org. no. 912638421 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK 247,000
Equity NOK 1.2m
Incorporated 2013
Share capital NOK 30,000

PIPE SUPPORT VERIFICATION AS is registered as a limited company in Asker, Akershus with organisation number 912638421. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av tjenester innen Olje- og energibransjen, hovedsaklig innenfor fagfeltet Piping & Layout.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK 247,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK 247,000
Equity
NOK 1.2m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns PIPE SUPPORT VERIFICATION AS?

JAN ØVERBY KÅLHUS
PIPE SUPPORT VERIFICATION AS
NOK 12.3m rev. · NOK 247,000 profit

PIPE SUPPORT VERIFICATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIPE SUPPORT VERIFICATION AS

Who owns PIPE SUPPORT VERIFICATION AS?

JAN ØVERBY KÅLHUS is the largest registered owner, with 100.0%.

What is the revenue of PIPE SUPPORT VERIFICATION AS?

PIPE SUPPORT VERIFICATION AS had revenue of NOK 12.3m in 2024.

Who is the general manager of PIPE SUPPORT VERIFICATION AS?

Jan Øverby Kålhus is registered as general manager of PIPE SUPPORT VERIFICATION AS.

Where is PIPE SUPPORT VERIFICATION AS based?

PIPE SUPPORT VERIFICATION AS has its business address in Borgen.

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.