BIZTRAC BETA
Rental and operating of own or leased real estate

BERGEN BYGG OG EIENDOM AS

Org. no. 918558160 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −321,000
Equity NOK −2.0m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−321k kr).

BERGEN BYGG OG EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 918558160. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Næringsvirksomhet, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −321,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −321,000
Equity
NOK −2.0m

Financial health · 2024

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

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

Who owns BERGEN BYGG OG EIENDOM AS?

EKRE INVEST AS
BERGEN BYGG OG EIENDOM AS
NOK 0 rev. · NOK −321,000 profit

BERGEN BYGG OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN BYGG OG EIENDOM AS

Who owns BERGEN BYGG OG EIENDOM AS?

EKRE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN BYGG OG EIENDOM AS?

BERGEN BYGG OG EIENDOM AS had revenue of NOK 0 in 2024.

Where is BERGEN BYGG OG EIENDOM AS based?

BERGEN BYGG OG EIENDOM AS has its business address in Hylkje.

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.