BIZTRAC BETA
Retail sale of motorcycles, motorcycle parts and accessories

MC LILLEHAMMER AS

Org. no. 988068314 Limited company (AS) Lillehammer Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK 293,000
Equity NOK 1.4m
Incorporated 2005
Share capital NOK 100,000

MC LILLEHAMMER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 988068314. The business is classified under retail sale of motorcycles, motorcycle parts and accessories (NACE 47.830). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Omsetning av og reparasjoner av motorkjøretøyer, salg av deler og utstyr til disse, samt annet hva hermed står i forbindelse. Selskapet skal kunne eie fast eiendom. ”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK 293,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK 293,000
Equity
NOK 1.4m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns MC LILLEHAMMER AS?

NILS ERIK ALMESTRAND
MC LILLEHAMMER AS
NOK 11.8m rev. · NOK 293,000 profit

MC LILLEHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MC LILLEHAMMER AS

Who owns MC LILLEHAMMER AS?

NILS ERIK ALMESTRAND is the largest registered owner, with 100.0%.

What is the revenue of MC LILLEHAMMER AS?

MC LILLEHAMMER AS had revenue of NOK 11.8m in 2024.

Who is the general manager of MC LILLEHAMMER AS?

Nils Erik Almestrand is registered as general manager of MC LILLEHAMMER AS.

Where is MC LILLEHAMMER AS based?

MC LILLEHAMMER AS has its business address in Lillehammer.

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.