BIZTRAC BETA
COMPANY REGISTER PROFILE
999594913 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

PRORA BOLIGPROSJEKTER AS

Org. no. 999594913 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Equity NOK 6,000
Incorporated 2013
Share capital NOK 30,000

PRORA BOLIGPROSJEKTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999594913. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i datterselskaper som driver med utvikling av boliger for salg.”.

Key figures · 2025

Equity
NOK 6,000
▲ +0 %
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns PRORA BOLIGPROSJEKTER AS?

PRORA BOLIGPROSJEKTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRORA BOLIGPROSJEKTER AS

Who owns PRORA BOLIGPROSJEKTER AS?

PRORA EIENDOM AS is the largest registered owner, with 80.0%.

Where is PRORA BOLIGPROSJEKTER AS based?

PRORA BOLIGPROSJEKTER AS has its business address in Trondheim.

Property

Business address Kjøpmannsgata 8, 7013 Trondheim
Cadastral unit 5001-400/142/0/0
Building Annen kontorbygning · 5 units

14 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.