BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

BVS UTLEIE AS

Org. no. 931950258 Limited company (AS) Øvre Eiker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 255,000
Operating profit NOK 180,000
Equity NOK 125,000
Incorporated 2023
Share capital NOK 30,000

BVS UTLEIE AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 931950258. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av verktøy, kjøp og salg av eiendom samt drift av annen virksomhet som står i forbindelse med dette, herunder deltagelse som eier i selskaper som driver slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 255,000 in revenue and NOK 180,000 in operating profit.

Key figures · 2024

Revenue
NOK 255,000
Operating profit
NOK 180,000
Equity
NOK 125,000
Est. value
NOK 618,000

Financial health · 2024

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

Who owns BVS UTLEIE AS?

JAN ARE RØREN
BVS UTLEIE AS
NOK 255,000 rev. · NOK 180,000 profit

BVS UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BVS UTLEIE AS own?

BVS UTLEIE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BVS UTLEIE AS

Who owns BVS UTLEIE AS?

JAN ARE RØREN is the largest registered owner, with 100.0%.

What is the revenue of BVS UTLEIE AS?

BVS UTLEIE AS had revenue of NOK 255,000 in 2024.

Where is BVS UTLEIE AS based?

BVS UTLEIE AS has its business address in Skotselv.

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.