BIZTRAC BETA
Other real estate activities on a fee or contract basis

PROAKTIV EIENDOM OG INVEST AS

Org. no. 916609841 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK 339,000
Incorporated 2015
Share capital NOK 300,000

Signals

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

PROAKTIV EIENDOM OG INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 916609841. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Drive forvaltning av eiendom og deltagelse i andre selskaper forøvrig, samt forvaltning av midler.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 339,000
Est. value
NOK 352,000

Financial health · 2024

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

Who owns PROAKTIV EIENDOM OG INVEST AS?

GEORG ANDRE GADE AS
PROAKTIV EIENDOM OG INVEST AS
NOK 0 rev. · NOK −17,000 profit

PROAKTIV EIENDOM OG INVEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROAKTIV EIENDOM OG INVEST AS

Who owns PROAKTIV EIENDOM OG INVEST AS?

GEORG ANDRE GADE AS is the largest registered owner, with 33.3%.

What is the revenue of PROAKTIV EIENDOM OG INVEST AS?

PROAKTIV EIENDOM OG INVEST AS had revenue of NOK 0 in 2024.

Where is PROAKTIV EIENDOM OG INVEST AS based?

PROAKTIV EIENDOM OG INVEST AS has its business address in Bergen.

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.