BIZTRAC BETA
Other captive investment companies

PRANGERØD PROJECTS AS

Org. no. 918842896 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −229,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PRANGERØD PROJECTS AS is registered as a limited company in Bærum, Akershus with organisation number 918842896. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i enterepenørskap og fast eiendom, samt annen virksomhet som faller naturlig sammen med dette.”.

Key figures · 2024

Operating profit
NOK −10,000
Equity
NOK −229,000

Financial health · 2024

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

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

Who owns PRANGERØD PROJECTS AS?

ELIN CATHRINE PRANGERØD
PRANGERØD PROJECTS AS
· NOK −10,000 profit

PRANGERØD PROJECTS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRANGERØD PROJECTS AS own?

PRANGERØD PROJECTS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PRANGERØD PROJECTS AS

Who owns PRANGERØD PROJECTS AS?

ELIN CATHRINE PRANGERØD is the largest registered owner, with 100.0%.

Who is the general manager of PRANGERØD PROJECTS AS?

Elin Cathrine Prangerød is registered as general manager of PRANGERØD PROJECTS AS.

Where is PRANGERØD PROJECTS AS based?

PRANGERØD PROJECTS AS has its business address in Stabekk.

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.