BIZTRAC BETA
Computer programming activities

TRON JOHAN WIIG AS

Org. no. 992191589 Limited company (AS) Ullensaker Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 305,000
Incorporated 2008
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

TRON JOHAN WIIG AS is registered as a limited company in Ullensaker, Akershus with organisation number 992191589. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet system og programvare, kjøp og salg av aksjer, kjøp og salg av fast eiendom samt dertil naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 305,000
Est. value
NOK 170,000

Financial health · 2025

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

Who owns TRON JOHAN WIIG AS?

TRON JOHAN WIIG
TRON JOHAN WIIG AS
NOK 0 rev. · NOK −6,000 profit

TRON JOHAN WIIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRON JOHAN WIIG AS own?

TRON JOHAN WIIG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRON JOHAN WIIG AS

Who owns TRON JOHAN WIIG AS?

TRON JOHAN WIIG is the largest registered owner, with 100.0%.

What is the revenue of TRON JOHAN WIIG AS?

TRON JOHAN WIIG AS had revenue of NOK 0 in 2025.

Where is TRON JOHAN WIIG AS based?

TRON JOHAN WIIG AS has its business address in Jessheim.

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.