BIZTRAC BETA
Uoppgitt

LARSSONS SPAREGRIS AS

Org. no. 925118028 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 1.3m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).
  • Nylig endring 2026-02-13 Adresseendring registrert 2026-02-13.

LARSSONS SPAREGRIS AS is registered as a limited company in Asker, Akershus with organisation number 925118028. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −28,000
Equity
NOK 1.3m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns LARSSONS SPAREGRIS AS?

NORMA LØVHAUGEN
LARSSONS SPAREGRIS AS
· NOK −28,000 profit

LARSSONS SPAREGRIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LARSSONS SPAREGRIS AS own?

LARSSONS SPAREGRIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LARSSONS SPAREGRIS AS

Who owns LARSSONS SPAREGRIS AS?

NORMA LØVHAUGEN is the largest registered owner, with 100.0%.

Who is the general manager of LARSSONS SPAREGRIS AS?

Norma Løvhaugen is registered as general manager of LARSSONS SPAREGRIS AS.

Where is LARSSONS SPAREGRIS AS based?

LARSSONS SPAREGRIS AS has its business address in Asker.

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.