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

LIPSCORE AS

Org. no. 932973618 Limited company (AS) Oslo Incorporated 2024 Active
Revenue 2025 NOK 37.8m
Operating profit NOK −8.2m
Equity NOK −4.8m
Incorporated 2024
Employees 9
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,8 mill kr).

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 9 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 2025 financial year, show NOK 37.8m in revenue and NOK −8.2m in operating profit.

Former names: NFH 240151 AS, LIPSCORE OPERATIONS AS

Key figures · 2025

Revenue
NOK 37.8m
▲ +41 %
Operating profit
NOK −8.2m
▲ +21 %
Equity
NOK −4.8m
▼ −350 %

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
-50.0%
Not satisfactory
Return on total assets
Solidity
-30.1%
Weak
Equity as a share of total capital

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

Who owns LIPSCORE AS?

LIPSCORE AS
NOK 37.8m rev. · NOK −8.2m 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 37.8m in 2025.

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

Report a problem

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