BIZTRAC BETA
COMPANY REGISTER PROFILE
991303715 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Development of building projects

BERGEN NÆRINGSBYGG AS

Org. no. 991303715 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −621,000
Equity NOK 21.6m
Incorporated 2007
Share capital NOK 80,000

Signals

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

BERGEN NÆRINGSBYGG AS is registered as a limited company in Bergen, Vestland with organisation number 991303715. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 80,000, divided into 80176 shares. The company's stated purpose is: “Eiendomsutvikling, konsulentvirksomhet og deltagelse i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −621,000
Equity
NOK 21.6m
Est. value
NOK 106.8m

Financial health · 2024

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

Who owns BERGEN NÆRINGSBYGG AS?

REGARD AS
BERGEN NÆRINGSBYGG AS
· NOK −621,000 profit

BERGEN NÆRINGSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGEN NÆRINGSBYGG AS own?

BERGEN NÆRINGSBYGG AS holds a stake in 1 company:

See the full ownership structure →

Group structure

BERGEN NÆRINGSBYGG AS er morselskap for 1 datterselskap:

Frequently asked questions about BERGEN NÆRINGSBYGG AS

Who owns BERGEN NÆRINGSBYGG AS?

REGARD AS is the largest registered owner, with 100.0%.

Who is the general manager of BERGEN NÆRINGSBYGG AS?

Trond Drager is registered as general manager of BERGEN NÆRINGSBYGG AS.

Where is BERGEN NÆRINGSBYGG AS based?

BERGEN NÆRINGSBYGG 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.