BIZTRAC BETA
Business and other management consultancy activities

PRONI INVEST AS

Org. no. 914765609 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 420,000
Operating profit NOK −15,000
Equity NOK 3.2m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).

PRONI INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 914765609. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby rådgivning, kursvirksomhet og annen konsulentbistand. Investering i selskaper, aksjer, eiendom og deler som hører naturlig sammen med dette m.m.”. The most recent filed accounts, for the 2024 financial year, show NOK 420,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 420,000
Operating profit
NOK −15,000
Equity
NOK 3.2m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns PRONI INVEST AS?

STIAN SIMONSEN
PRONI INVEST AS
NOK 420,000 rev. · NOK −15,000 profit

PRONI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRONI INVEST AS own?

PRONI INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about PRONI INVEST AS

Who owns PRONI INVEST AS?

STIAN SIMONSEN is the largest registered owner, with 100.0%.

What is the revenue of PRONI INVEST AS?

PRONI INVEST AS had revenue of NOK 420,000 in 2024.

Where is PRONI INVEST AS based?

PRONI INVEST AS has its business address in Oslo.

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.