BIZTRAC BETA
Other captive investment companies

LAYSAN HOLDING AS

Org. no. 917274363 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −63,000
Equity NOK −189,000
Incorporated 2016
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−189k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−63k kr).
  • Nylig endring 2026-04-15 Adresseendring registrert 2026-04-15.

LAYSAN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 917274363. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap, virksomhet består i å investere i og eie aksjer, finansielle instrumenter og andeler i andre selskaper som det til enhver tid finner hensiktsmessig, samt annen virksomhet som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −63,000
Equity
NOK −189,000

Financial health · 2024

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

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

Who owns LAYSAN HOLDING AS?

LARS ROGER THOMAS
LAYSAN HOLDING AS
· NOK −63,000 profit

LAYSAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAYSAN HOLDING AS own?

LAYSAN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LAYSAN HOLDING AS

Who owns LAYSAN HOLDING AS?

LARS ROGER THOMAS is the largest registered owner, with 100.0%.

Where is LAYSAN HOLDING AS based?

LAYSAN HOLDING 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.