BIZTRAC BETA
Computer consultancy and computer facilities management activities

VIXLY AS

Org. no. 991768777 Limited company (AS) Tromsø Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −5.1m
Equity NOK 2.6m
Incorporated 2007
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,1 mill kr).

VIXLY AS is registered as a limited company in Tromsø, Troms with organisation number 991768777. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2007. Registered share capital is NOK 1.5m, divided into 15198 shares. The company's stated purpose is: “Direkte eller indirekte å drive virksomhet med utvikling og salg av teknologibaserte produkter og tjenester og alt som står i forbindelse med dette, samt deltagelse og investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −5.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −5.1m
Equity
NOK 2.6m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns VIXLY AS?

GHIBLI AS
VIXLY AS
NOK 2.5m rev. · NOK −5.1m profit

VIXLY AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about VIXLY AS

Who owns VIXLY AS?

GHIBLI AS is the largest registered owner, with 18.2%.

What is the revenue of VIXLY AS?

VIXLY AS had revenue of NOK 2.5m in 2024.

Who is the general manager of VIXLY AS?

Kjell Øystein Moe Øksendal is registered as general manager of VIXLY AS.

Where is VIXLY AS based?

VIXLY AS has its business address in Tromsø.

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.