BIZTRAC BETA
Uoppgitt

PEMAKAP AS

Org. no. 928700631 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −295,000
Equity NOK 185.1m
Incorporated 2022
Share capital NOK 2.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−295k kr).
  • Nylig endring 2026-05-23 Aksjekapital registrert 2026-05-23.

PEMAKAP AS is registered as a limited company in Oslo, Oslo with organisation number 928700631. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 2.2m, divided into 2403 shares. The company's stated purpose is: “Selskapets formål er investeringer i aksjer, andeler og andre verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egenkapital, lån eller ved avgivelse av garantier.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −295,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −295,000
Equity
NOK 185.1m
Est. value
NOK 217.5m

Financial health · 2024

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

Who owns PEMAKAP AS?

BODIL KATRINE STEEN
PEMAKAP AS
NOK 0 rev. · NOK −295,000 profit

PEMAKAP AS has 8 registered shareholders:

All shareholders and roles →

Which companies does PEMAKAP AS own?

PEMAKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PEMAKAP AS

Who owns PEMAKAP AS?

BODIL KATRINE STEEN is the largest registered owner, with 13.9%.

What is the revenue of PEMAKAP AS?

PEMAKAP AS had revenue of NOK 0 in 2024.

Where is PEMAKAP AS based?

PEMAKAP 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.