BIZTRAC BETA
Computer programming activities

LUUPS AS

Org. no. 926766856 Limited company (AS) Volda Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 802,000
Operating profit NOK −360,000
Equity NOK −333,000
Incorporated 2021
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−333k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−360k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-29 Adresseendring registrert 2026-04-29.

LUUPS AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 926766856. 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: “Utvikling og salg av tenester innan visuell kommunikasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 802,000 in revenue and NOK −360,000 in operating profit.

Key figures · 2025

Revenue
NOK 802,000
Operating profit
NOK −360,000
Equity
NOK −333,000

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-31.7%
Weak
Equity as a share of total capital

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

Who owns LUUPS AS?

OCLIN HOLDING AS
LUUPS AS
NOK 802,000 rev. · NOK −360,000 profit

LUUPS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUUPS AS

Who owns LUUPS AS?

OCLIN HOLDING AS is the largest registered owner, with 93.3%.

What is the revenue of LUUPS AS?

LUUPS AS had revenue of NOK 802,000 in 2025.

Where is LUUPS AS based?

LUUPS AS has its business address in Volda.

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.