biztrac. BETA
COMPANY REGISTER PROFILE
827495042 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

LEARNIX AS

Org. no. 827495042 Limited company (AS) Asker Incorporated 2021 Active
Revenue 2025 NOK 100,000
Operating profit NOK −5,000
Equity NOK 12,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

LEARNIX AS is registered as a limited company in Asker, Akershus with organisation number 827495042. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av programvareprodukter, programvarekonsulent, programvare utvikling, digital markedsføring, høyteknologisk kompetanse coaching. Arrangering av arrangementer og begivenheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK −5,000 in operating profit.

Former names: COMARTEK AS

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK −5,000
▲ +57 %
Equity
NOK 12,000
▼ −31 %
Est. value
NOK 174,000

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
-18.9%
Not satisfactory
Return on total assets
Solidity
30.4%
Weak
Equity as a share of total capital

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

Who owns LEARNIX AS?

LEARNIX AS
NOK 100,000 rev. · NOK −5,000 profit

LEARNIX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEARNIX AS

Who owns LEARNIX AS?

Giang Huong Le is the largest registered owner, with 100.0%.

What is the revenue of LEARNIX AS?

LEARNIX AS had revenue of NOK 100,000 in 2025.

Where is LEARNIX AS based?

LEARNIX AS has its business address in Asker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.