BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

BUSKERUD BILUTLEIE AS

Org. no. 921989865 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 1.1m
Equity NOK 2.7m
Incorporated 2018
Share capital NOK 30,000

BUSKERUD BILUTLEIE AS is registered as a limited company in Drammen, Buskerud with organisation number 921989865. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av person-, vare og lastebiler, med dertil hørende virksomhet. Inkludert salg og forsikringer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 1.1m
Equity
NOK 2.7m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns BUSKERUD BILUTLEIE AS?

YEL HOLDING AS
BUSKERUD BILUTLEIE AS
NOK 13.2m rev. · NOK 1.1m profit

BUSKERUD BILUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSKERUD BILUTLEIE AS

Who owns BUSKERUD BILUTLEIE AS?

YEL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BUSKERUD BILUTLEIE AS?

BUSKERUD BILUTLEIE AS had revenue of NOK 13.2m in 2024.

Who is the general manager of BUSKERUD BILUTLEIE AS?

Ali Osman Yel is registered as general manager of BUSKERUD BILUTLEIE AS.

Where is BUSKERUD BILUTLEIE AS based?

BUSKERUD BILUTLEIE 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.