BIZTRAC BETA
Rental and operating of own or leased real estate

LENSMANNSLIA 30 AS

Org. no. 992004622 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 1.1m
Equity NOK 6.8m
Incorporated 2007
Share capital NOK 3.0m

LENSMANNSLIA 30 AS is registered as a limited company in Bærum, Akershus with organisation number 992004622. 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 3.0m, divided into 3000 shares. The company's stated purpose is: “Erverv, utvikling, drift, forvaltning og salg av fast eiendom, samt det som naturlig står i forhold til dette, foruten deltakelse i andre selskaper med lignende formål samt erverv av aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 1.1m
Equity
NOK 6.8m
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns LENSMANNSLIA 30 AS?

ENDER INVEST AS
LENSMANNSLIA 30 AS
NOK 4.4m rev. · NOK 1.1m profit

LENSMANNSLIA 30 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LENSMANNSLIA 30 AS

Who owns LENSMANNSLIA 30 AS?

ENDER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LENSMANNSLIA 30 AS?

LENSMANNSLIA 30 AS had revenue of NOK 4.4m in 2024.

Who is the general manager of LENSMANNSLIA 30 AS?

Erik Cato Ender is registered as general manager of LENSMANNSLIA 30 AS.

Where is LENSMANNSLIA 30 AS based?

LENSMANNSLIA 30 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.