BIZTRAC BETA
Repair and maintenance of motor vehicles

KONNERUD BILSHINE AS

Org. no. 932882914 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −49,000
Equity NOK 48,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−49k kr).

KONNERUD BILSHINE AS is registered as a limited company in Drammen, Buskerud with organisation number 932882914. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Vask og vedlikehold av bil.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −49,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −49,000
Equity
NOK 48,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.3%
Weak
Equity as a share of total capital

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

Who owns KONNERUD BILSHINE AS?

REBAZ SALAR NORI SALEH
KONNERUD BILSHINE AS
NOK 2.7m rev. · NOK −49,000 profit

KONNERUD BILSHINE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONNERUD BILSHINE AS

Who owns KONNERUD BILSHINE AS?

REBAZ SALAR NORI SALEH is the largest registered owner, with 50.0%.

What is the revenue of KONNERUD BILSHINE AS?

KONNERUD BILSHINE AS had revenue of NOK 2.7m in 2025.

Who is the general manager of KONNERUD BILSHINE AS?

Rebaz Salar Nori Saleh is registered as general manager of KONNERUD BILSHINE AS.

Where is KONNERUD BILSHINE AS based?

KONNERUD BILSHINE AS has its business address in Drammen.

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.