BIZTRAC BETA
Computer programming activities

VIIDRE AS

Org. no. 936662382 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-03.

VIIDRE AS is registered as a limited company in Oslo, Oslo with organisation number 936662382. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 21,000
Est. value
NOK 38,000

Financial health · 2025

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

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

Who owns VIIDRE AS?

HARALDSØ HOLDING AS
VIIDRE AS
NOK 0 rev. · NOK −2,000 profit

VIIDRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIIDRE AS

Who owns VIIDRE AS?

HARALDSØ HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VIIDRE AS?

VIIDRE AS had revenue of NOK 0 in 2025.

Who is the general manager of VIIDRE AS?

Nicolay Aarstad Wildhagen is registered as general manager of VIIDRE AS.

Where is VIIDRE AS based?

VIIDRE AS has its business address in Oslo.

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.