BIZTRAC BETA
Computer programming activities

LIPSCORE AS

Org. no. 932973618 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 26.9m
Operating profit NOK −10.4m
Equity NOK 1.9m
Incorporated 2024
Employees 12
Share capital NOK 150,000

Signals

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

LIPSCORE AS is registered as a limited company in Oslo, Oslo with organisation number 932973618. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024 and has 12 registered employees. Registered share capital is NOK 150,000, divided into 3000 shares. The company's stated purpose is: “Holdingselskap. Investering i aksjer og øvrige verdipapirer, eiendom og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.9m in revenue and NOK −10.4m in operating profit.

Key figures · 2024

Revenue
NOK 26.9m
Operating profit
NOK −10.4m
Equity
NOK 1.9m
Est. value
NOK 45.1m

Financial health · 2024

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

Who owns LIPSCORE AS?

LIPSCORE INTERNATIONAL AS
LIPSCORE AS
NOK 26.9m rev. · NOK −10.4m profit

LIPSCORE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIPSCORE AS

Who owns LIPSCORE AS?

LIPSCORE INTERNATIONAL AS is the largest registered owner, with 100.0%.

What is the revenue of LIPSCORE AS?

LIPSCORE AS had revenue of NOK 26.9m in 2024.

Where is LIPSCORE AS based?

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