BIZTRAC BETA
Publishing of video games

AUDVYR AS

Org. no. 921244037 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 18,000
Operating profit NOK −2,000
Equity NOK 3,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

AUDVYR AS is registered as a limited company in Oslo, Oslo with organisation number 921244037. The business is classified under publishing of video games (NACE 58.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon av dataspill, interaktive opplevelser, digitale og fysiske kunstneriske produkter samt konsulenttjenester og enhver annen virksomhet som naturlig står i forhold til disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 18,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 18,000
Operating profit
NOK −2,000
Equity
NOK 3,000
Est. value
NOK 32,000

Financial health · 2024

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

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

Who owns AUDVYR AS?

STIAN MOFOSSBAKKE WILLUMS
AUDVYR AS
NOK 18,000 rev. · NOK −2,000 profit

AUDVYR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUDVYR AS

Who owns AUDVYR AS?

STIAN MOFOSSBAKKE WILLUMS is the largest registered owner, with 100.0%.

What is the revenue of AUDVYR AS?

AUDVYR AS had revenue of NOK 18,000 in 2024.

Who is the general manager of AUDVYR AS?

Stian Mofossbakke Willums is registered as general manager of AUDVYR AS.

Where is AUDVYR AS based?

AUDVYR 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.