BIZTRAC BETA
Rental and operating of own or leased real estate

JSL EIENDOM AS

Org. no. 919350415 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 2.0m
Equity NOK 4.4m
Incorporated 2017
Share capital NOK 480,000

JSL EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 919350415. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 480,000, divided into 1600 shares. The company's stated purpose is: “Tilby utleie, utvikling, drift av fast eiendom samt annen virksomhet som naturlig faller sammen med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 2.0m
Equity
NOK 4.4m
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns JSL EIENDOM AS?

NAHEED AKHTAR
JSL EIENDOM AS
NOK 2.0m rev. · NOK 2.0m profit

JSL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JSL EIENDOM AS own?

JSL EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JSL EIENDOM AS

Who owns JSL EIENDOM AS?

NAHEED AKHTAR is the largest registered owner, with 100.0%.

What is the revenue of JSL EIENDOM AS?

JSL EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of JSL EIENDOM AS?

Shazeb Ismail Akhtar is registered as general manager of JSL EIENDOM AS.

Where is JSL EIENDOM AS based?

JSL EIENDOM AS has its business address in Oslo.

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.