BIZTRAC BETA
Rental and operating of own or leased real estate

LAGÅRDSVEIEN 44 AS

Org. no. 992042842 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 45.4m
Operating profit NOK 23.1m
Equity NOK 315.7m
Incorporated 2007
Share capital NOK 1.5m

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 44 AS is registered as a limited company in Bærum, Akershus with organisation number 992042842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.5m, divided into 1 shares. The company's stated purpose is: “Selskapets virksomhet er å 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 45.4m in revenue and NOK 23.1m in operating profit.

Key figures · 2024

Revenue
NOK 45.4m
Operating profit
NOK 23.1m
Equity
NOK 315.7m
Est. value
NOK 282.5m

Financial health · 2024

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

Who owns LAGÅRDSVEIEN 44 AS?

SEN HOLDING AS
LAGÅRDSVEIEN 44 AS
NOK 45.4m rev. · NOK 23.1m profit

LAGÅRDSVEIEN 44 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAGÅRDSVEIEN 44 AS

Who owns LAGÅRDSVEIEN 44 AS?

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

What is the revenue of LAGÅRDSVEIEN 44 AS?

LAGÅRDSVEIEN 44 AS had revenue of NOK 45.4m in 2024.

Where is LAGÅRDSVEIEN 44 AS based?

LAGÅRDSVEIEN 44 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.