BIZTRAC BETA
Computer programming activities

CLOP LABS AS

Org. no. 934361466 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

CLOP LABS AS is registered as a limited company in Oslo, Oslo with organisation number 934361466. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programmering - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 44,000

Financial health · 2024

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

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

Who owns CLOP LABS AS?

HOLHJEM DEVELOPMENT AS
CLOP LABS AS
NOK 0 rev. · NOK −6,000 profit

CLOP LABS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLOP LABS AS

Who owns CLOP LABS AS?

HOLHJEM DEVELOPMENT AS is the largest registered owner, with 50.0%.

What is the revenue of CLOP LABS AS?

CLOP LABS AS had revenue of NOK 0 in 2024.

Who is the general manager of CLOP LABS AS?

Håkon Holhjem is registered as general manager of CLOP LABS AS.

Where is CLOP LABS AS based?

CLOP LABS 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.