BIZTRAC BETA
Uoppgitt

APEC AS

Org. no. 932367262 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 1.8m
Incorporated 2023
Share capital NOK 30,000

Signals

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

APEC AS is registered as a limited company in Bærum, Akershus with organisation number 932367262. 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.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 1.8m
Est. value
NOK 12.6m

Financial health · 2025

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

Who owns APEC AS?

PETER JOHAN PRAN
APEC AS
NOK 0 rev. · NOK −16,000 profit

APEC AS has 2 registered shareholders:

All shareholders and roles →

Which companies does APEC AS own?

APEC AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about APEC AS

Who owns APEC AS?

PETER JOHAN PRAN is the largest registered owner, with 50.0%.

What is the revenue of APEC AS?

APEC AS had revenue of NOK 0 in 2024.

Who is the general manager of APEC AS?

Peter Johan Pran is registered as general manager of APEC AS.

Where is APEC AS based?

APEC AS has its business address in Jar.

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.