BIZTRAC BETA
Rental and operating of own or leased real estate

JEKYLL HOLDING AS

Org. no. 898200582 Limited company (AS) Kristiansand Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 474,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

JEKYLL HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 898200582. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer og selskapsandeler i andre selskaper og investerer i alle former for form finansaktiva samt fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 474,000
Est. value
NOK 432,000

Financial health · 2025

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

Who owns JEKYLL HOLDING AS?

SIGMUND VIK
JEKYLL HOLDING AS
NOK 0 rev. · NOK −4,000 profit

JEKYLL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JEKYLL HOLDING AS own?

JEKYLL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JEKYLL HOLDING AS

Who owns JEKYLL HOLDING AS?

SIGMUND VIK is the largest registered owner, with 100.0%.

What is the revenue of JEKYLL HOLDING AS?

JEKYLL HOLDING AS had revenue of NOK 0 in 2025.

Where is JEKYLL HOLDING AS based?

JEKYLL HOLDING AS has its business address in Kristiansand S.

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.