BIZTRAC BETA
Retail sale of motor vehicles

M.R AUTOHAWK AS

Org. no. 920319297 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 247,000
Equity NOK 675,000
Incorporated 2018
Share capital NOK 45,000

M.R AUTOHAWK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920319297. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2018. Registered share capital is NOK 45,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av biler samt import av biler fra utlandet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 247,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 247,000
Equity
NOK 675,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns M.R AUTOHAWK AS?

MANZOOR AHMAD
M.R AUTOHAWK AS
NOK 9.5m rev. · NOK 247,000 profit

M.R AUTOHAWK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M.R AUTOHAWK AS

Who owns M.R AUTOHAWK AS?

MANZOOR AHMAD is the largest registered owner, with 100.0%.

What is the revenue of M.R AUTOHAWK AS?

M.R AUTOHAWK AS had revenue of NOK 9.5m in 2024.

Who is the general manager of M.R AUTOHAWK AS?

Ali Frhan Ahmad is registered as general manager of M.R AUTOHAWK AS.

Where is M.R AUTOHAWK AS based?

M.R AUTOHAWK AS has its business address in Skedsmokorset.

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.