BIZTRAC BETA
Rental and operating of own or leased real estate

LAGÅRDSVEIEN 46 AS

Org. no. 889558822 Limited company (AS) Bærum Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 41.8m
Operating profit NOK 30.3m
Equity NOK 29.4m
Incorporated 2006
Share capital NOK 1.0m

Signals

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

LAGÅRDSVEIEN 46 AS is registered as a limited company in Bærum, Akershus with organisation number 889558822. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1 shares. The company's stated purpose is: “Å eie, utvikle, forvalte, utleie, kjøp og salg av fast eiendom og alt som hermed står i forbindelse, herunder delta i andre selskap med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 41.8m in revenue and NOK 30.3m in operating profit.

Key figures · 2024

Revenue
NOK 41.8m
Operating profit
NOK 30.3m
Equity
NOK 29.4m
Est. value
NOK 71.9m

Financial health · 2024

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

Who owns LAGÅRDSVEIEN 46 AS?

SEN HOLDING AS
LAGÅRDSVEIEN 46 AS
NOK 41.8m rev. · NOK 30.3m profit

LAGÅRDSVEIEN 46 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAGÅRDSVEIEN 46 AS

Who owns LAGÅRDSVEIEN 46 AS?

SEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LAGÅRDSVEIEN 46 AS?

LAGÅRDSVEIEN 46 AS had revenue of NOK 41.8m in 2024.

Where is LAGÅRDSVEIEN 46 AS based?

LAGÅRDSVEIEN 46 AS has its business address in Lysaker.

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.