BIZTRAC BETA
Rental and operating of own or leased real estate

LINK BERGEN AS

Org. no. 923763406 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −283,000
Equity NOK 85.0m
Incorporated 2019
Share capital NOK 6.5m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−282k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LINK BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 923763406. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 6.5m, divided into 5000 shares. The company's stated purpose is: “Å eie og forvalte eiendom, deltagelse i andre selskaper samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −283,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −283,000
Equity
NOK 85.0m
Est. value
NOK 77.6m

Financial health · 2024

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

Who owns LINK BERGEN AS?

BARA EIENDOM AS
LINK BERGEN AS
NOK 0 rev. · NOK −283,000 profit

LINK BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LINK BERGEN AS er morselskap for 12 datterselskaper:

Frequently asked questions about LINK BERGEN AS

Who owns LINK BERGEN AS?

BARA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LINK BERGEN AS?

LINK BERGEN AS had revenue of NOK 0 in 2024.

Where is LINK BERGEN AS based?

LINK BERGEN 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.