BIZTRAC BETA
Retail sale of clothing

LIMAMI AS

Org. no. 894911972 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 10.6m
Operating profit NOK 389,000
Equity NOK 461,000
Incorporated 2009
Employees 17
Share capital NOK 100,000

LIMAMI AS is registered as a limited company in Bærum, Akershus with organisation number 894911972. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2009 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, drift samt kjøp og salg av fast eiendom samt alt som naturlig står i forbindelse med dette, derunder investeringer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.6m in revenue and NOK 389,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.6m
Operating profit
NOK 389,000
Equity
NOK 461,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns LIMAMI AS?

THOMAS ALEXANDERSEN
LIMAMI AS
NOK 10.6m rev. · NOK 389,000 profit

LIMAMI AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIMAMI AS own?

LIMAMI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIMAMI AS

Who owns LIMAMI AS?

THOMAS ALEXANDERSEN is the largest registered owner, with 51.0%.

What is the revenue of LIMAMI AS?

LIMAMI AS had revenue of NOK 10.6m in 2024.

Who is the general manager of LIMAMI AS?

Hanne Skullerud Alexandersen is registered as general manager of LIMAMI AS.

Where is LIMAMI AS based?

LIMAMI AS has its business address in Blommenholm.

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.