BIZTRAC BETA
Computer programming activities

VOQDR AS

Org. no. 929362454 Limited company (AS) Narvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK −276,000
Equity NOK 872,000
Incorporated 2022
Share capital NOK 2.5m

Signals

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

VOQDR AS is registered as a limited company in Narvik, Nordland with organisation number 929362454. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 2.5m, divided into 1000 shares. The company's stated purpose is: “Selge egenutviklede tjenester. Virksomheten kan drives av selskapet selv, av datterselskaper eller gjennom deltakelse i andre selskaper eller i samarbeid med andre. Selskapet kan også delta i annen økonomisk virksomhet, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK −276,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK −276,000
Equity
NOK 872,000
Est. value
NOK 564,000

Financial health · 2025

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

Who owns VOQDR AS?

FACERE AS
VOQDR AS
NOK 100,000 rev. · NOK −276,000 profit

VOQDR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOQDR AS

Who owns VOQDR AS?

FACERE AS is the largest registered owner, with 50.0%.

What is the revenue of VOQDR AS?

VOQDR AS had revenue of NOK 100,000 in 2025.

Who is the general manager of VOQDR AS?

Florian Aschwanden is registered as general manager of VOQDR AS.

Where is VOQDR AS based?

VOQDR AS has its business address in Narvik.

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.