BIZTRAC BETA
Accounting and bookkeeping

APP ACCOUNTING AS

Org. no. 933665755 Limited company (AS) Indre Østfold Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 9,000
Operating profit NOK −6,000
Equity NOK 88,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

APP ACCOUNTING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 933665755. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskapsførervirksomhet og rådgivning for eksterne kunder og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 9,000
Operating profit
NOK −6,000
Equity
NOK 88,000
Est. value
NOK 52,000

Financial health · 2024

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

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

Who owns APP ACCOUNTING AS?

SAMURAI AS
APP ACCOUNTING AS
NOK 9,000 rev. · NOK −6,000 profit

APP ACCOUNTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about APP ACCOUNTING AS

Who owns APP ACCOUNTING AS?

SAMURAI AS is the largest registered owner, with 66.0%.

What is the revenue of APP ACCOUNTING AS?

APP ACCOUNTING AS had revenue of NOK 9,000 in 2024.

Who is the general manager of APP ACCOUNTING AS?

Knut Inge Brænd is registered as general manager of APP ACCOUNTING AS.

Where is APP ACCOUNTING AS based?

APP ACCOUNTING AS has its business address in Askim.

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.