BIZTRAC BETA
Computer consultancy and computer facilities management activities

WONKA AS

Org. no. 922723788 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 74,000
Operating profit NOK 49,000
Equity NOK 24,000
Incorporated 2019
Share capital NOK 30,000

WONKA AS is registered as a limited company in Oslo, Oslo with organisation number 922723788. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen teknologi, programvareutvikling, systemarkitektur, rådgivning og tilhørende virksomhet. Selskapet kan også drive investeringer og annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 74,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 74,000
Operating profit
NOK 49,000
Equity
NOK 24,000
Est. value
NOK 146,000

Financial health · 2025

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

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

Who owns WONKA AS?

KINE SKJERVUM-KARLSEN
WONKA AS
NOK 74,000 rev. · NOK 49,000 profit

WONKA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WONKA AS

Who owns WONKA AS?

KINE SKJERVUM-KARLSEN is the largest registered owner, with 50.0%.

What is the revenue of WONKA AS?

WONKA AS had revenue of NOK 74,000 in 2025.

Who is the general manager of WONKA AS?

Iver Skjervum-Karlsen is registered as general manager of WONKA AS.

Where is WONKA AS based?

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