BIZTRAC BETA
Rental and operating of own or leased real estate

JAGUKASE AS

Org. no. 932272687 Limited company (AS) Time Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 13,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

JAGUKASE AS is registered as a limited company in Time, Rogaland with organisation number 932272687. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av fast eiendom - og annet som naturlig faller sammen med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 13,000
Est. value
NOK 12,000

Financial health · 2025

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

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

Who owns JAGUKASE AS?

JAN SERIGSTAD
JAGUKASE AS
NOK 0 rev. · NOK −6,000 profit

JAGUKASE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JAGUKASE AS own?

JAGUKASE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JAGUKASE AS

Who owns JAGUKASE AS?

JAN SERIGSTAD is the largest registered owner, with 50.0%.

What is the revenue of JAGUKASE AS?

JAGUKASE AS had revenue of NOK 0 in 2025.

Where is JAGUKASE AS based?

JAGUKASE AS has its business address in Lye.

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.