BIZTRAC BETA
Computer programming activities

VIRTUR AS

Org. no. 931450506 Limited company (AS) Inderøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 240,000
Operating profit NOK −11.0m
Equity NOK −3.5m
Incorporated 2023
Employees 8
Share capital NOK 10.0m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11,0 mill kr).
  • Nylig endring 2026-02-04 Aksjekapital registrert 2026-02-04.

VIRTUR AS is registered as a limited company in Inderøy, Trøndelag with organisation number 931450506. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 10.0m, divided into 10000000 shares. The company's stated purpose is: “Programvareselskap for utvikling og utleie/salg av programvare til bruk i bilsimulator og virksomheter som er tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 240,000 in revenue and NOK −11.0m in operating profit.

Key figures · 2024

Revenue
NOK 240,000
Operating profit
NOK −11.0m
Equity
NOK −3.5m

Financial health · 2024

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

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

Who owns VIRTUR AS?

KØRVEN AS
VIRTUR AS
NOK 240,000 rev. · NOK −11.0m profit

VIRTUR AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about VIRTUR AS

Who owns VIRTUR AS?

KØRVEN AS is the largest registered owner, with 40.6%.

What is the revenue of VIRTUR AS?

VIRTUR AS had revenue of NOK 240,000 in 2024.

Where is VIRTUR AS based?

VIRTUR AS has its business address in Inderøy.

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.