BIZTRAC BETA
Buying and selling of own real estate

PK-WEUM INVEST AS

Org. no. 919667451 Limited company (AS) Askøy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 1.5m
Incorporated 2017
Share capital NOK 30,000

Signals

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

PK-WEUM INVEST AS is registered as a limited company in Askøy, Vestland with organisation number 919667451. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og andeler, kjøp og salg av eiendommer, og alt som står i forbindelse. Selskapet kan også delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 1.5m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns PK-WEUM INVEST AS?

PER KRISTIAN WEUM KNUDSEN
PK-WEUM INVEST AS
NOK 0 rev. · NOK −8,000 profit

PK-WEUM INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PK-WEUM INVEST AS own?

PK-WEUM INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PK-WEUM INVEST AS

Who owns PK-WEUM INVEST AS?

PER KRISTIAN WEUM KNUDSEN is the largest registered owner, with 100.0%.

What is the revenue of PK-WEUM INVEST AS?

PK-WEUM INVEST AS had revenue of NOK 0 in 2024.

Where is PK-WEUM INVEST AS based?

PK-WEUM INVEST AS has its business address in Strusshamn.

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.