BIZTRAC BETA
Rental and operating of own or leased real estate

JSL HOLDING AS

Org. no. 989133756 Limited company (AS) Stange Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 1.2m
Incorporated 2005
Share capital NOK 225,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

JSL HOLDING AS is registered as a limited company in Stange, Innlandet with organisation number 989133756. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 225,000, divided into 225 shares. The company's stated purpose is: “Investering i andre selskaper, samt hva derved står i sammenheng. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 1.2m
Est. value
NOK 928,000

Financial health · 2025

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

Who owns JSL HOLDING AS?

THORBJØRG HOLAGER LUND
JSL HOLDING AS
NOK 0 rev. · NOK −10,000 profit

JSL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JSL HOLDING AS own?

JSL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JSL HOLDING AS

Who owns JSL HOLDING AS?

THORBJØRG HOLAGER LUND is the largest registered owner, with 100.0%.

What is the revenue of JSL HOLDING AS?

JSL HOLDING AS had revenue of NOK 0 in 2025.

Where is JSL HOLDING AS based?

JSL HOLDING AS has its business address in Stange.

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.