BIZTRAC BETA
Computer programming activities

AP-PERFORMANCE HOLDING AS

Org. no. 920365957 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK −50,000
Incorporated 2018
Share capital NOK 40,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−50k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

AP-PERFORMANCE HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 920365957. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap for datterselskaper av AP-Performance holding, andre investeringer gjort av selskapet og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK −50,000

Financial health · 2025

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 AP-PERFORMANCE HOLDING AS?

ANDREAS ANGELTVEIT
AP-PERFORMANCE HOLDING AS
· NOK −13,000 profit

AP-PERFORMANCE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AP-PERFORMANCE HOLDING AS own?

AP-PERFORMANCE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AP-PERFORMANCE HOLDING AS

Who owns AP-PERFORMANCE HOLDING AS?

ANDREAS ANGELTVEIT is the largest registered owner, with 100.0%.

Where is AP-PERFORMANCE HOLDING AS based?

AP-PERFORMANCE HOLDING AS has its business address in Larvik.

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.