BIZTRAC BETA
Development of building projects

WINDPO PROPERTY AS

Org. no. 927890763 Limited company (AS) Eigersund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −81,000
Equity NOK −758,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−758k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).

WINDPO PROPERTY AS is registered as a limited company in Eigersund, Rogaland with organisation number 927890763. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av eiendommer, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −81,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −81,000
Equity
NOK −758,000

Financial health · 2024

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-31.9%
Weak
Equity as a share of total capital

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

Who owns WINDPO PROPERTY AS?

WINDPO AS
WINDPO PROPERTY AS
NOK 0 rev. · NOK −81,000 profit

WINDPO PROPERTY AS has 3 registered shareholders:

All shareholders and roles →

Group structure

WINDPO PROPERTY AS er morselskap for 5 datterselskaper:

Frequently asked questions about WINDPO PROPERTY AS

Who owns WINDPO PROPERTY AS?

WINDPO AS is the largest registered owner, with 70.0%.

What is the revenue of WINDPO PROPERTY AS?

WINDPO PROPERTY AS had revenue of NOK 0 in 2024.

Where is WINDPO PROPERTY AS based?

WINDPO PROPERTY AS has its business address in Egersund.

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.