BIZTRAC BETA
Uoppgitt

PARCAPE III AS

Org. no. 934078950 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 18,000
Incorporated 2024
Share capital NOK 40,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-08 Aksjekapital registrert 2026-04-08.

PARCAPE III AS is registered as a limited company in Oslo, Oslo with organisation number 934078950. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 10000 shares. The company's stated purpose is: “Å eie shipping-/offshore- og andre fartøy, andre realaktiva, samt å investere i andre selskap, og alt som dermed står i forbindelse, herunder utleie av skip på time charter- og bareboatvilkår. Selskapet skal som skipseiende aktør opptre langsiktig og drive aktiv skipsfart med fokus på optimal drift, samt grundig og løpende vedlikehold av sine skip.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 18,000
Est. value
NOK 22,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 PARCAPE III AS?

PARETO BUSINESS MANAGEMENT AS
PARCAPE III AS
· NOK −4,000 profit

PARCAPE III AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARCAPE III AS

Who owns PARCAPE III AS?

PARETO BUSINESS MANAGEMENT AS is the largest registered owner, with 100.0%.

Where is PARCAPE III AS based?

PARCAPE III 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 15.06.2026.

Report a problem

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