BIZTRAC BETA
Rental and operating of own or leased real estate

BERGVIKVEIEN 9 EIENDOM AS

Org. no. 914277124 Limited company (AS) Evenes Incorporated 1927 Active
Ownership graph ↗
Revenue 2024 NOK 880,000
Operating profit NOK 662,000
Equity NOK 2.7m
Incorporated 1927
Share capital NOK 150,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BERGVIKVEIEN 9 EIENDOM AS is registered as a limited company in Evenes, Nordland with organisation number 914277124. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1927. Registered share capital is NOK 150,000. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 880,000 in revenue and NOK 662,000 in operating profit.

Key figures · 2024

Revenue
NOK 880,000
Operating profit
NOK 662,000
Equity
NOK 2.7m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns BERGVIKVEIEN 9 EIENDOM AS?

I K LYKKE EIENDOM AS
BERGVIKVEIEN 9 EIENDOM AS
NOK 880,000 rev. · NOK 662,000 profit

BERGVIKVEIEN 9 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGVIKVEIEN 9 EIENDOM AS

Who owns BERGVIKVEIEN 9 EIENDOM AS?

I K LYKKE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BERGVIKVEIEN 9 EIENDOM AS?

BERGVIKVEIEN 9 EIENDOM AS had revenue of NOK 880,000 in 2024.

Where is BERGVIKVEIEN 9 EIENDOM AS based?

BERGVIKVEIEN 9 EIENDOM AS has its business address in Bogen I Ofoten.

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.