biztrac. BETA
COMPANY REGISTER PROFILE
926790641 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BERGSLYST BOLIG AS

Org. no. 926790641 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −157,000
Equity NOK −178,000
Incorporated 2021
Share capital NOK 60,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−178k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−157k kr).
  • Nylig endring 2026-06-17 Aksjekapital registrert 2026-06-17.

BERGSLYST BOLIG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926790641. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom, herunder kjøp og salg av grunnareal, bygg og eiendomsprosjekter, samt investering i andre selskaper med slik virksomhet.”.

Former names: EIENDOMSGRUPPEN UTVIKLING TRONDHEIM AS, BEKKEVOLLDALEN BOLIG AS

Key figures · 2025

Operating profit
NOK −157,000
▼ −265 %
Equity
NOK −178,000
▼ −890 %

Financial health · 2025

Liquidity
51.05
Very good
Current assets ÷ current liabilities
Profitability
-3.1%
Not satisfactory
Return on total assets
Solidity
-3.5%
Weak
Equity as a share of total capital

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

Who owns BERGSLYST BOLIG AS?

BERGSLYST BOLIG AS
· NOK −157,000 profit

BERGSLYST BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGSLYST BOLIG AS

Who owns BERGSLYST BOLIG AS?

EIENDOMSGRUPPEN AS is the largest registered owner, with 50.0%.

Where is BERGSLYST BOLIG AS based?

BERGSLYST BOLIG AS has its business address in Trondheim.

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

Report a problem

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