BIZTRAC BETA
Rental and operating of own or leased real estate

LY EIENDOM BERGENSGATA 9 AS

Org. no. 999000193 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 2.3m
Equity NOK 273,000
Incorporated 2012
Share capital NOK 76,000

Signals

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

LY EIENDOM BERGENSGATA 9 AS is registered as a limited company in Bærum, Akershus with organisation number 999000193. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 76,000, divided into 76000 shares. The company's stated purpose is: “Investering, forvaltning, konsulentvirksomhet, management og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 2.3m
Equity
NOK 273,000
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Not satisfactory
Equity as a share of total capital

Who owns LY EIENDOM BERGENSGATA 9 AS?

ARFR AS
LY EIENDOM BERGENSGATA 9 AS
NOK 2.6m rev. · NOK 2.3m profit

LY EIENDOM BERGENSGATA 9 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LY EIENDOM BERGENSGATA 9 AS

Who owns LY EIENDOM BERGENSGATA 9 AS?

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

What is the revenue of LY EIENDOM BERGENSGATA 9 AS?

LY EIENDOM BERGENSGATA 9 AS had revenue of NOK 2.6m in 2024.

Where is LY EIENDOM BERGENSGATA 9 AS based?

LY EIENDOM BERGENSGATA 9 AS has its business address in Bekkestua.

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.