BIZTRAC BETA
Computer programming activities

AVAILY UTVIKLING AS

Org. no. 827608912 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 64,000
Operating profit NOK −5.0m
Equity NOK 5.1m
Incorporated 2021
Share capital NOK 1.7m

Signals

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

AVAILY UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 827608912. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 1.7m, divided into 1651603 shares. The company's stated purpose is: “Internett tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 64,000 in revenue and NOK −5.0m in operating profit.

Key figures · 2024

Revenue
NOK 64,000
Operating profit
NOK −5.0m
Equity
NOK 5.1m
Est. value
NOK 9.3m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.0%
Very good
Equity as a share of total capital

Who owns AVAILY UTVIKLING AS?

LUCIENNE AS
AVAILY UTVIKLING AS
NOK 64,000 rev. · NOK −5.0m profit

AVAILY UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AVAILY UTVIKLING AS own?

AVAILY UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AVAILY UTVIKLING AS

Who owns AVAILY UTVIKLING AS?

LUCIENNE AS is the largest registered owner, with 100.0%.

What is the revenue of AVAILY UTVIKLING AS?

AVAILY UTVIKLING AS had revenue of NOK 64,000 in 2024.

Where is AVAILY UTVIKLING AS based?

AVAILY UTVIKLING 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.