BIZTRAC BETA
Rental and operating of own or leased real estate

PAPAYA HOLDING AS

Org. no. 922036713 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −862,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−862k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

PAPAYA HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 922036713. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom. Selskapet kan og eie aksjer i andre selskaper med tilsvarende eller annen virksomhet.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK −862,000

Financial health · 2024

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

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

Who owns PAPAYA HOLDING AS?

Petter Andreas Lundekvam
PAPAYA HOLDING AS
· NOK −3,000 profit

PAPAYA HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does PAPAYA HOLDING AS own?

PAPAYA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PAPAYA HOLDING AS

Who owns PAPAYA HOLDING AS?

Petter Andreas Lundekvam is the largest registered owner, with 60.0%.

Who is the general manager of PAPAYA HOLDING AS?

Per Arne Lundekvam is registered as general manager of PAPAYA HOLDING AS.

Where is PAPAYA HOLDING AS based?

PAPAYA HOLDING AS has its business address in Bergen.

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.