BIZTRAC BETA
Computer programming activities

WIN CONSULT AS

Org. no. 918882510 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 38,000
Operating profit NOK −73,000
Equity NOK −1.0m
Incorporated 2017
Share capital NOK 33,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−73k kr).

WIN CONSULT AS is registered as a limited company in Bærum, Akershus with organisation number 918882510. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 33,000, divided into 30000 shares. The company's stated purpose is: “Levere IT tjenester (programmering og rådgivning).”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
Operating profit
NOK −73,000
Equity
NOK −1.0m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7984.3%
Weak
Equity as a share of total capital

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

Who owns WIN CONSULT AS?

Tharmavanan Tharmalingam
WIN CONSULT AS
NOK 38,000 rev. · NOK −73,000 profit

WIN CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIN CONSULT AS

Who owns WIN CONSULT AS?

Tharmavanan Tharmalingam is the largest registered owner, with 100.0%.

What is the revenue of WIN CONSULT AS?

WIN CONSULT AS had revenue of NOK 38,000 in 2025.

Who is the general manager of WIN CONSULT AS?

Tharmavanan Tharmalingam is registered as general manager of WIN CONSULT AS.

Where is WIN CONSULT AS based?

WIN CONSULT AS has its business address in Kolsås.

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.