BIZTRAC BETA
Retail sale of motor vehicles

ROSENBORG MOTOR AS

Org. no. 926461850 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 152,000
Equity NOK −243,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−243k kr).
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

ROSENBORG MOTOR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926461850. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av bruktbiler.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 152,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 152,000
Equity
NOK −243,000
Est. value
NOK 799,000

Financial health · 2025

Liquidity
-23.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-96.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ROSENBORG MOTOR AS?

YASIN INAL
ROSENBORG MOTOR AS
NOK 4.0m rev. · NOK 152,000 profit

ROSENBORG MOTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROSENBORG MOTOR AS

Who owns ROSENBORG MOTOR AS?

YASIN INAL is the largest registered owner, with 100.0%.

What is the revenue of ROSENBORG MOTOR AS?

ROSENBORG MOTOR AS had revenue of NOK 4.0m in 2025.

Who is the general manager of ROSENBORG MOTOR AS?

Yasin Inal is registered as general manager of ROSENBORG MOTOR AS.

Where is ROSENBORG MOTOR AS based?

ROSENBORG MOTOR AS has its business address in Trondheim.

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.