BIZTRAC BETA
Retail sale of motor vehicles

AUTOPARTNER OSLO AS

Org. no. 815278682 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK 819,000
Equity NOK 4.4m
Incorporated 2015
Share capital NOK 30,000

AUTOPARTNER OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 815278682. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av biler og andre transportmidler samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK 819,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK 819,000
Equity
NOK 4.4m
Est. value
NOK 6.1m

Financial health · 2024

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

Who owns AUTOPARTNER OSLO AS?

AMIR SHAYAN SHAPIRI
AUTOPARTNER OSLO AS
NOK 16.1m rev. · NOK 819,000 profit

AUTOPARTNER OSLO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AUTOPARTNER OSLO AS own?

AUTOPARTNER OSLO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AUTOPARTNER OSLO AS

Who owns AUTOPARTNER OSLO AS?

AMIR SHAYAN SHAPIRI is the largest registered owner, with 100.0%.

What is the revenue of AUTOPARTNER OSLO AS?

AUTOPARTNER OSLO AS had revenue of NOK 16.1m in 2024.

Who is the general manager of AUTOPARTNER OSLO AS?

Amir Shayan Shapiri is registered as general manager of AUTOPARTNER OSLO AS.

Where is AUTOPARTNER OSLO AS based?

AUTOPARTNER OSLO AS has its business address in Oslo.

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.