BIZTRAC BETA
Development of building projects

PORSGRUNN NÆRINGSPARK HOLDING AS

Org. no. 929614801 Limited company (AS) Porsgrunn Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −209,000
Equity NOK 66.3m
Incorporated 2022
Share capital NOK 63,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−209k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PORSGRUNN NÆRINGSPARK HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 929614801. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 63,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2024

Operating profit
NOK −209,000
Equity
NOK 66.3m
Est. value
NOK 293.9m

Financial health · 2024

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

Who owns PORSGRUNN NÆRINGSPARK HOLDING AS?

PORSGRUNN EIENDOMSINVEST AS
PORSGRUNN NÆRINGSPARK HOLDING AS
· NOK −209,000 profit

PORSGRUNN NÆRINGSPARK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PORSGRUNN NÆRINGSPARK HOLDING AS own?

PORSGRUNN NÆRINGSPARK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PORSGRUNN NÆRINGSPARK HOLDING AS

Who owns PORSGRUNN NÆRINGSPARK HOLDING AS?

PORSGRUNN EIENDOMSINVEST AS is the largest registered owner, with 100.0%.

Where is PORSGRUNN NÆRINGSPARK HOLDING AS based?

PORSGRUNN NÆRINGSPARK HOLDING 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.