BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

WIPCO AS

Org. no. 950024895 Limited company (AS) Nesodden Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 126.8m
Operating profit NOK 5.5m
Equity NOK 8.5m
Incorporated 1988
Employees 28
Share capital NOK 150,000

WIPCO AS is registered as a limited company in Nesodden, Akershus with organisation number 950024895. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1988 and has 28 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Konsulent- og rådgivningsvirksomhet innen næringslivet og for privatpersoner. Dessuten ved aksjetegning eller på annen måte delta i næringsvirksomhet. Selskapet skal også drive med ervervelse og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 126.8m in revenue and NOK 5.5m in operating profit.

Key figures · 2024

Revenue
NOK 126.8m
Operating profit
NOK 5.5m
Equity
NOK 8.5m
Est. value
NOK 25.4m

Financial health · 2024

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

Who owns WIPCO AS?

KÅRE LORANG SVENDSEN
WIPCO AS
NOK 126.8m rev. · NOK 5.5m profit

WIPCO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about WIPCO AS

Who owns WIPCO AS?

KÅRE LORANG SVENDSEN is the largest registered owner, with 33.3%.

What is the revenue of WIPCO AS?

WIPCO AS had revenue of NOK 126.8m in 2024.

Who is the general manager of WIPCO AS?

Roar Johansen is registered as general manager of WIPCO AS.

Where is WIPCO AS based?

WIPCO AS has its business address in Nesoddtangen.

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.