BIZTRAC BETA
Computer programming activities

KVASS AS

Org. no. 926045873 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK −2.6m
Equity NOK 91.0m
Incorporated 2020
Share capital NOK 27.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVASS AS is registered as a limited company in Oslo, Oslo with organisation number 926045873. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 27.0m, divided into 270000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i og delta i andre selskaper med et hvilket som helst formål, samt investere i fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK −2.6m in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK −2.6m
Equity
NOK 91.0m
Est. value
NOK 51.9m

Financial health · 2024

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

Who owns KVASS AS?

ALFANOR 19195 AS
KVASS AS
NOK 6.3m rev. · NOK −2.6m profit

KVASS AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does KVASS AS own?

KVASS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KVASS AS

Who owns KVASS AS?

ALFANOR 19195 AS is the largest registered owner, with 44.9%.

What is the revenue of KVASS AS?

KVASS AS had revenue of NOK 6.3m in 2024.

Where is KVASS AS based?

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