BIZTRAC BETA
Rental and operating of own or leased real estate

INVESTPOL AS

Org. no. 829722682 Limited company (AS) Askøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 463,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

INVESTPOL AS is registered as a limited company in Askøy, Vestland with organisation number 829722682. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andre verdipapirer, investering, utvikling og drift av fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 463,000
Est. value
NOK 340,000

Financial health · 2025

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

Who owns INVESTPOL AS?

PIOTR POLINSKI
INVESTPOL AS
NOK 0 rev. · NOK −14,000 profit

INVESTPOL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INVESTPOL AS own?

INVESTPOL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INVESTPOL AS

Who owns INVESTPOL AS?

PIOTR POLINSKI is the largest registered owner, with 100.0%.

What is the revenue of INVESTPOL AS?

INVESTPOL AS had revenue of NOK 0 in 2025.

Where is INVESTPOL AS based?

INVESTPOL AS has its business address in Herdla.

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.