BIZTRAC BETA
Rental and operating of own or leased real estate

PROSPECTIVE UTVIKLING AS

Org. no. 918830588 Limited company (AS) Porsgrunn Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −57,000
Equity NOK −147,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PROSPECTIVE UTVIKLING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 918830588. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2024

Operating profit
NOK −57,000
Equity
NOK −147,000

Financial health · 2024

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

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

Who owns PROSPECTIVE UTVIKLING AS?

G1 HOLDING AS
PROSPECTIVE UTVIKLING AS
· NOK −57,000 profit

PROSPECTIVE UTVIKLING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PROSPECTIVE UTVIKLING AS own?

PROSPECTIVE UTVIKLING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PROSPECTIVE UTVIKLING AS

Who owns PROSPECTIVE UTVIKLING AS?

G1 HOLDING AS is the largest registered owner, with 28.3%.

Where is PROSPECTIVE UTVIKLING AS based?

PROSPECTIVE UTVIKLING AS has its business address in Porsgrunn.

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.