BIZTRAC BETA
Plumbing installation

ANDRESEN OG SØNN AS

Org. no. 985169136 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 28.5m
Operating profit NOK 4.0m
Equity NOK 5.4m
Incorporated 2002
Employees 14
Share capital NOK 100,000

ANDRESEN OG SØNN AS is registered as a limited company in Oslo, Oslo with organisation number 985169136. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2002 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet og salg av tilhørende produkter. Selskapet kan også delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer og verdipapirer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.5m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 28.5m
Operating profit
NOK 4.0m
Equity
NOK 5.4m
Est. value
NOK 13.7m

Financial health · 2025

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

Who owns ANDRESEN OG SØNN AS?

JOHN ARNE ANDRESEN
ANDRESEN OG SØNN AS
NOK 28.5m rev. · NOK 4.0m profit

ANDRESEN OG SØNN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANDRESEN OG SØNN AS

Who owns ANDRESEN OG SØNN AS?

JOHN ARNE ANDRESEN is the largest registered owner, with 50.0%.

What is the revenue of ANDRESEN OG SØNN AS?

ANDRESEN OG SØNN AS had revenue of NOK 28.5m in 2025.

Who is the general manager of ANDRESEN OG SØNN AS?

Patrick Andresen is registered as general manager of ANDRESEN OG SØNN AS.

Where is ANDRESEN OG SØNN AS based?

ANDRESEN OG SØNN 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.