BIZTRAC BETA
COMPANY REGISTER PROFILE
997671953 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

LSA INVEST AS

Org. no. 997671953 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Equity NOK 13.9m
Incorporated 2011
Share capital NOK 100,000

LSA INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 997671953. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og/eller drive fast eiendom og investere i andre selskaper, og alt som dermed står i forbindelse.”.

Key figures · 2025

Equity
NOK 13.9m
▲ +24 %
Est. value
NOK 19.5m

Financial health · 2025

Liquidity
151.49
Very good
Current assets ÷ current liabilities
Profitability
28.7%
Very good
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns LSA INVEST AS?

LSA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LSA INVEST AS own?

LSA INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LSA INVEST AS

Who owns LSA INVEST AS?

SVEN IVER HEGSTAD is the largest registered owner, with 100.0%.

Where is LSA INVEST AS based?

LSA INVEST AS has its business address in Jar.

Property

Business address c/o Hegstad Gimleveien 5, 1358 Jar
Cadastral unit 3201-20/23/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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