BIZTRAC BETA
COMPANY REGISTER PROFILE
932686902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

POTET HOLDING AS

Org. no. 932686902 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 11,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

POTET HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 932686902. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns POTET HOLDING AS?

POTET HOLDING AS
· NOK −7,000 profit

POTET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POTET HOLDING AS own?

POTET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POTET HOLDING AS

Who owns POTET HOLDING AS?

BJØRN OLAV SALVESEN is the largest registered owner, with 100.0%.

Who is the general manager of POTET HOLDING AS?

Bjørn Olav Salvesen is registered as general manager of POTET HOLDING AS.

Where is POTET HOLDING AS based?

POTET HOLDING 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 25.08.2026.

Report a problem

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