BIZTRAC BETA
Retail sale of motor vehicles

ROMERIKE AUTOHUS AS

Org. no. 917338795 Limited company (AS) Ullensaker Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 80.2m
Operating profit NOK 5.6m
Equity NOK 10.6m
Incorporated 2016
Share capital NOK 100,000

ROMERIKE AUTOHUS AS is registered as a limited company in Ullensaker, Akershus with organisation number 917338795. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg biler 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 80.2m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 80.2m
Operating profit
NOK 5.6m
Equity
NOK 10.6m
Est. value
NOK 29.0m

Financial health · 2024

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

Who owns ROMERIKE AUTOHUS AS?

TARIQ ISMAIL
ROMERIKE AUTOHUS AS
NOK 80.2m rev. · NOK 5.6m profit

ROMERIKE AUTOHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE AUTOHUS AS

Who owns ROMERIKE AUTOHUS AS?

TARIQ ISMAIL is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE AUTOHUS AS?

ROMERIKE AUTOHUS AS had revenue of NOK 80.2m in 2024.

Who is the general manager of ROMERIKE AUTOHUS AS?

Irbaz Tariq is registered as general manager of ROMERIKE AUTOHUS AS.

Where is ROMERIKE AUTOHUS AS based?

ROMERIKE AUTOHUS AS has its business address in Kløfta.

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.