BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

LEMALOU AS

Org. no. 928539237 Limited company (AS) Gjerdrum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 775,000
Operating profit NOK −8,000
Equity NOK 18,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

LEMALOU AS is registered as a limited company in Gjerdrum, Akershus with organisation number 928539237. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Internetthandel/varehandel av hageartikler, klær og interiør. Selskapet kan også selge håndverkstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 775,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 775,000
Operating profit
NOK −8,000
Equity
NOK 18,000
Est. value
NOK 261,000

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LEMALOU AS?

KENT MATTIAS LJUNGGREN
LEMALOU AS
NOK 775,000 rev. · NOK −8,000 profit

LEMALOU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEMALOU AS

Who owns LEMALOU AS?

KENT MATTIAS LJUNGGREN is the largest registered owner, with 100.0%.

What is the revenue of LEMALOU AS?

LEMALOU AS had revenue of NOK 775,000 in 2025.

Who is the general manager of LEMALOU AS?

Kent Mattias Ljunggren is registered as general manager of LEMALOU AS.

Where is LEMALOU AS based?

LEMALOU AS has its business address in Gjerdrum.

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.