biztrac. BETA
COMPANY REGISTER PROFILE
935720699 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

JLS HOLDING AS

Org. no. 935720699 Limited company (AS) Lillesand Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −7
Equity NOK 33,000
Incorporated 2025
Share capital NOK 40,000

Signals

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

JLS HOLDING AS is registered as a limited company in Lillesand, Agder with organisation number 935720699. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investeringsvirksomhet og kjøp, salg og forvaltning av fast eiendom og andre formuesobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7
Equity
NOK 33,000
Est. value
NOK 61,000

Financial health · 2025

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

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

Who owns JLS HOLDING AS?

JLS HOLDING AS
NOK 0 rev. · NOK −7 profit

JLS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JLS HOLDING AS own?

JLS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JLS HOLDING AS

Who owns JLS HOLDING AS?

Jan Lewi Skeie is the largest registered owner, with 100.0%.

What is the revenue of JLS HOLDING AS?

JLS HOLDING AS had revenue of NOK 0 in 2025.

Where is JLS HOLDING AS based?

JLS HOLDING AS has its business address in Lillesand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.