BIZTRAC BETA
COMPANY REGISTER PROFILE
822608132 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

APPSTER AS

Org. no. 822608132 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −71,000
Equity NOK 316,000
Incorporated 2019
Share capital NOK 250,000

Signals

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

APPSTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 822608132. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Utvikling av mobilapplikasjoner samt alt som hermed hører med.”.

Key figures · 2025

Operating profit
NOK −71,000
Equity
NOK 316,000
Est. value
NOK 572,000

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.3%
Very good
Equity as a share of total capital

Who owns APPSTER AS?

APPSTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about APPSTER AS

Who owns APPSTER AS?

HENRIK DRAGSNES JØRGENSEN is the largest registered owner, with 50.0%.

Where is APPSTER AS based?

APPSTER AS has its business address in Trondheim.

Property

Business address v/Ottesen Dyre Halses gate 16, 7042 Trondheim
Cadastral unit 5001-410/686/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 25 units

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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