BIZTRAC BETA
Rental and operating of own or leased real estate

L-SPAR AS

Org. no. 999564305 Limited company (AS) Aurskog-Høland Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 84,000
Operating profit NOK −99,000
Equity NOK 24.3m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−99k kr).

L-SPAR AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 999564305. 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 30,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer, utleie av fast eiendom, og øvrig investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 84,000 in revenue and NOK −99,000 in operating profit.

Key figures · 2024

Revenue
NOK 84,000
Operating profit
NOK −99,000
Equity
NOK 24.3m
Est. value
NOK 19.2m

Financial health · 2024

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

Who owns L-SPAR AS?

SIGMUND LINDVIK
L-SPAR AS
NOK 84,000 rev. · NOK −99,000 profit

L-SPAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does L-SPAR AS own?

L-SPAR AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about L-SPAR AS

Who owns L-SPAR AS?

SIGMUND LINDVIK is the largest registered owner, with 100.0%.

What is the revenue of L-SPAR AS?

L-SPAR AS had revenue of NOK 84,000 in 2024.

Who is the general manager of L-SPAR AS?

Sigmund Lindvik is registered as general manager of L-SPAR AS.

Where is L-SPAR AS based?

L-SPAR AS has its business address in Aurskog.

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.