BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

OSLO BOBILUTLEIE AS

Org. no. 924699000 Limited company (AS) Gran Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 660,000
Operating profit NOK −543,000
Equity NOK −1.1m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−543k kr).

OSLO BOBILUTLEIE AS is registered as a limited company in Gran, Innlandet with organisation number 924699000. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av bobiler og campingbiler samt virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 660,000 in revenue and NOK −543,000 in operating profit.

Key figures · 2024

Revenue
NOK 660,000
Operating profit
NOK −543,000
Equity
NOK −1.1m

Financial health · 2024

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

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

Who owns OSLO BOBILUTLEIE AS?

FNORDLI HOLDING AS
OSLO BOBILUTLEIE AS
NOK 660,000 rev. · NOK −543,000 profit

OSLO BOBILUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BOBILUTLEIE AS

Who owns OSLO BOBILUTLEIE AS?

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

What is the revenue of OSLO BOBILUTLEIE AS?

OSLO BOBILUTLEIE AS had revenue of NOK 660,000 in 2024.

Where is OSLO BOBILUTLEIE AS based?

OSLO BOBILUTLEIE AS has its business address in Jaren.

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.