biztrac. BETA
COMPANY REGISTER PROFILE
930104973 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

BYENS AUTOSALG AS

Org. no. 930104973 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 13.9m
Operating profit NOK −586,000
Equity NOK 637,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BYENS AUTOSALG AS is registered as a limited company in Larvik, Vestfold with organisation number 930104973. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av brukte biler.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.9m in revenue and NOK −586,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.9m
▲ +49 %
Operating profit
NOK −586,000
▼ −136 %
Equity
NOK 637,000
▼ −48 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
2.47
Very good
Current assets ÷ current liabilities
Profitability
-32.1%
Not satisfactory
Return on total assets
Solidity
40.6%
Very good
Equity as a share of total capital

Who owns BYENS AUTOSALG AS?

BYENS AUTOSALG AS
NOK 13.9m rev. · NOK −586,000 profit

BYENS AUTOSALG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYENS AUTOSALG AS

Who owns BYENS AUTOSALG AS?

Kateb Mohammed Salim is the largest registered owner, with 100.0%.

What is the revenue of BYENS AUTOSALG AS?

BYENS AUTOSALG AS had revenue of NOK 13.9m in 2025.

Who is the general manager of BYENS AUTOSALG AS?

Edita Degimaite is registered as general manager of BYENS AUTOSALG AS.

Where is BYENS AUTOSALG AS based?

BYENS AUTOSALG AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.