biztrac. BETA
COMPANY REGISTER PROFILE
926705881 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

PROPCON AS

Org. no. 926705881 Limited company (AS) Stavanger Incorporated 2021 Active
Operating profit NOK −32,000
Equity NOK −36,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−36k kr).

PROPCON AS is registered as a limited company in Stavanger, Rogaland with organisation number 926705881. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Å eie eller delta i foretak som driver investerings-, forretnings- , eller finansieringsvirksomhet og virksomhet som er forbundet med dette innenfor rammen av den til enhver tid gjeldende lovgivning. Industri, handel, finansiering, erverv og salg av verdipapirer og andre investeringer, kjøp, salg, utvikling og drift av fast eiendom, drift av media, tjenesteytelser, og enhver annen virksomhet i sammenheng med det her nevnte. Virksomheten drives av selskapet selv eller gjennom dets datterselskap i inn- og utland.”.

Key figures · 2025

Operating profit
NOK −32,000
▼ −49 %
Equity
NOK −36,000
▼ −563 %

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-567.2%
Weak
Equity as a share of total capital

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

Who owns PROPCON AS?

PROPCON AS
· NOK −32,000 profit

PROPCON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROPCON AS

Who owns PROPCON AS?

GULLP INVEST AS is the largest registered owner, with 100.0%.

Where is PROPCON AS based?

PROPCON AS has its business address in Hundvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.