BIZTRAC BETA
Rental and operating of own or leased real estate

LUND ASKER AS

Org. no. 999228070 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 13.6m
Operating profit NOK 2.5m
Equity NOK 73.7m
Incorporated 2012
Share capital NOK 470,000

Signals

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

LUND ASKER AS is registered as a limited company in Oslo, Oslo with organisation number 999228070. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 470,000, divided into 235000 shares. The company's stated purpose is: “Eiendomsforvaltning og investeringsvirksomhet av enhver art i egen regi eller gjennom deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.6m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 13.6m
Operating profit
NOK 2.5m
Equity
NOK 73.7m
Est. value
NOK 56.0m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.4%
Very good
Equity as a share of total capital

Who owns LUND ASKER AS?

L. A. LUND AS
LUND ASKER AS
NOK 13.6m rev. · NOK 2.5m profit

LUND ASKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUND ASKER AS

Who owns LUND ASKER AS?

L. A. LUND AS is the largest registered owner, with 100.0%.

What is the revenue of LUND ASKER AS?

LUND ASKER AS had revenue of NOK 13.6m in 2024.

Who is the general manager of LUND ASKER AS?

Peter Henrik Svarstad is registered as general manager of LUND ASKER AS.

Where is LUND ASKER AS based?

LUND ASKER AS has its business address in Oslo.

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.