BIZTRAC BETA
Buying and selling of own real estate

BOLIGPROSJEKT ØST AS

Org. no. 986934952 Limited company (AS) Nord-Fron Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −45,000
Equity NOK 10.2m
Incorporated 2004
Share capital NOK 106,000

Signals

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

BOLIGPROSJEKT ØST AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 986934952. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2004. Registered share capital is NOK 106,000, divided into 105600 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av forskjellig art, utleie av maskiner, utstyr og eiendom, entreprenør- og konsulenttjenester av forskjellig art innen bygg og anlegg, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −45,000
Equity
NOK 10.2m
Est. value
NOK 9.3m

Financial health · 2024

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

Who owns BOLIGPROSJEKT ØST AS?

OLA STORMORKEN
BOLIGPROSJEKT ØST AS
· NOK −45,000 profit

BOLIGPROSJEKT ØST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BOLIGPROSJEKT ØST AS own?

BOLIGPROSJEKT ØST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BOLIGPROSJEKT ØST AS

Who owns BOLIGPROSJEKT ØST AS?

OLA STORMORKEN is the largest registered owner, with 100.0%.

Who is the general manager of BOLIGPROSJEKT ØST AS?

Ola Stormorken is registered as general manager of BOLIGPROSJEKT ØST AS.

Where is BOLIGPROSJEKT ØST AS based?

BOLIGPROSJEKT ØST AS has its business address in Kvam.

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.