BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

LEASEPRO AS

Org. no. 926755870 Limited company (AS) Porsgrunn Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 845,000
Operating profit NOK −627,000
Equity NOK −352,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−352k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−627k kr).

LEASEPRO AS is registered as a limited company in Porsgrunn, Telemark with organisation number 926755870. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av kjøretøy, maskiner og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 845,000 in revenue and NOK −627,000 in operating profit.

Key figures · 2024

Revenue
NOK 845,000
Operating profit
NOK −627,000
Equity
NOK −352,000

Financial health · 2024

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

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

Who owns LEASEPRO AS?

BERU HOLDING AS
LEASEPRO AS
NOK 845,000 rev. · NOK −627,000 profit

LEASEPRO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEASEPRO AS

Who owns LEASEPRO AS?

BERU HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of LEASEPRO AS?

LEASEPRO AS had revenue of NOK 845,000 in 2024.

Who is the general manager of LEASEPRO AS?

Petter Bjørnvald Olsen is registered as general manager of LEASEPRO AS.

Where is LEASEPRO AS based?

LEASEPRO AS has its business address in Porsgrunn.

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.