BIZTRAC BETA
Retail sale of footwear and leather goods

LE'GANZ STRØMMEN AS

Org. no. 898805522 Limited company (AS) Lillestrøm Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 283,000
Equity NOK 945,000
Incorporated 2012
Employees 6
Share capital NOK 100,000

LE'GANZ STRØMMEN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 898805522. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2012 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handelsvirksomhet, og dermed beslektet virksomhet. Gjennom aksjetegning etter på annen måte skal selskapet kunne delt i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 283,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 283,000
Equity
NOK 945,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns LE'GANZ STRØMMEN AS?

LE'GANZ GRUPPEN AS
LE'GANZ STRØMMEN AS
NOK 7.2m rev. · NOK 283,000 profit

LE'GANZ STRØMMEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LE'GANZ STRØMMEN AS

Who owns LE'GANZ STRØMMEN AS?

LE'GANZ GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of LE'GANZ STRØMMEN AS?

LE'GANZ STRØMMEN AS had revenue of NOK 7.2m in 2024.

Who is the general manager of LE'GANZ STRØMMEN AS?

Ole Sverre Mengkrog is registered as general manager of LE'GANZ STRØMMEN AS.

Where is LE'GANZ STRØMMEN AS based?

LE'GANZ STRØMMEN AS has its business address in Strømmen.

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.