BIZTRAC BETA
Business and other management consultancy activities

VIDDA HOLDING AS

Org. no. 923169733 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 24,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

VIDDA HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 923169733. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskaper og gi veiledning og råd til nylig etablerte bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 24,000
Est. value
NOK 40,000

Financial health · 2025

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

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

Who owns VIDDA HOLDING AS?

MARTIN LANGELO LIEN
VIDDA HOLDING AS
NOK 0 rev. · NOK −11,000 profit

VIDDA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIDDA HOLDING AS

Who owns VIDDA HOLDING AS?

MARTIN LANGELO LIEN is the largest registered owner, with 100.0%.

What is the revenue of VIDDA HOLDING AS?

VIDDA HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of VIDDA HOLDING AS?

Martin Langelo Lien is registered as general manager of VIDDA HOLDING AS.

Where is VIDDA HOLDING AS based?

VIDDA HOLDING AS has its business address in Hvalstad.

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.