BIZTRAC BETA
Uoppgitt

PSM INVEST 2 AS

Org. no. 829217082 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −25,000
Equity NOK 69,000
Incorporated 2022
Share capital NOK 191,000

Signals

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

PSM INVEST 2 AS is registered as a limited company in Oslo, Oslo with organisation number 829217082. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 191,000, divided into 190500 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av verdipapirer og fast eiendom, og hva som står i forbindelse, herunder eie selskaper som har slikt formål, samt selskaper med andre formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 69,000
Est. value
NOK 81,000

Financial health · 2025

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

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

Who owns PSM INVEST 2 AS?

VESPER INVEST AS
PSM INVEST 2 AS
NOK 0 rev. · NOK −25,000 profit

PSM INVEST 2 AS has 3 registered shareholders:

All shareholders and roles →

Which companies does PSM INVEST 2 AS own?

PSM INVEST 2 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PSM INVEST 2 AS

Who owns PSM INVEST 2 AS?

VESPER INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of PSM INVEST 2 AS?

PSM INVEST 2 AS had revenue of NOK 0 in 2025.

Where is PSM INVEST 2 AS based?

PSM INVEST 2 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.