BIZTRAC BETA
Industrial product and fashion design activities

CONWIG AS

Org. no. 930376620 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 12,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

CONWIG AS is registered as a limited company in Bærum, Akershus with organisation number 930376620. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Design av og bygging av konstruksjoner, konsept design av konstruksjoner og løsninger, enten direkte eller gjennom aksjeeie, deltakelse i andre selskaper og alt som dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 12,000
Est. value
NOK 20,000

Financial health · 2024

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

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

Who owns CONWIG AS?

JAN WIGAARD
CONWIG AS
NOK 0 rev. · NOK −4,000 profit

CONWIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CONWIG AS own?

CONWIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CONWIG AS

Who owns CONWIG AS?

JAN WIGAARD is the largest registered owner, with 100.0%.

What is the revenue of CONWIG AS?

CONWIG AS had revenue of NOK 0 in 2025.

Where is CONWIG AS based?

CONWIG AS has its business address in Hosle.

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.