BIZTRAC BETA
Retail sale of clothing

MAXIMA MOTE LILLESTRØM AS

Org. no. 998935296 Limited company (AS) Lillestrøm Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 189,000
Equity NOK 288,000
Incorporated 2012
Share capital NOK 400,000

MAXIMA MOTE LILLESTRØM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 998935296. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2012. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Salg av klær og andre produkter som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 189,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
Operating profit
NOK 189,000
Equity
NOK 288,000
Est. value
NOK 790,000

Financial health · 2025

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

Who owns MAXIMA MOTE LILLESTRØM AS?

BERIT HERMANSEN
MAXIMA MOTE LILLESTRØM AS
NOK 7.8m rev. · NOK 189,000 profit

MAXIMA MOTE LILLESTRØM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAXIMA MOTE LILLESTRØM AS

Who owns MAXIMA MOTE LILLESTRØM AS?

BERIT HERMANSEN is the largest registered owner, with 51.0%.

What is the revenue of MAXIMA MOTE LILLESTRØM AS?

MAXIMA MOTE LILLESTRØM AS had revenue of NOK 7.8m in 2025.

Who is the general manager of MAXIMA MOTE LILLESTRØM AS?

Berit Hermansen is registered as general manager of MAXIMA MOTE LILLESTRØM AS.

Where is MAXIMA MOTE LILLESTRØM AS based?

MAXIMA MOTE LILLESTRØM AS has its business address in Lillestrøm.

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.