biztrac. BETA
COMPANY REGISTER PROFILE
889558822 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 42.6m
Operating profit NOK 31.3m
Equity NOK 28.6m
Incorporated 2006
Share capital NOK 1.0m

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 2025 financial year, show NOK 42.6m in revenue and NOK 31.3m in operating profit.

Former names: INVESTORPROSJEKT IV AS, LAGÅRDSVEIEN HOLDING AS

Key figures · 2025

Revenue
NOK 42.6m
▲ +2 %
Operating profit
NOK 31.3m
▲ +3 %
Equity
NOK 28.6m
▼ −3 %
Est. value
NOK 80.5m

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
10.1%
Good
Return on total assets
Solidity
12.9%
Satisfactory
Equity as a share of total capital

Who owns LAGÅRDSVEIEN 46 AS?

LAGÅRDSVEIEN 46 AS
NOK 42.6m rev. · NOK 31.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 42.6m in 2025.

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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.