biztrac. BETA
COMPANY REGISTER PROFILE
933448851 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

JUR HOLDING AS

Org. no. 933448851 Limited company (AS) Gjesdal Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 1.3m
Incorporated 2024
Share capital NOK 120,000

Signals

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

JUR HOLDING AS is registered as a limited company in Gjesdal, Rogaland with organisation number 933448851. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 120,000, divided into 15000 shares. The company's stated purpose is: “Eie og investere i aksjer og andre verdipapirer, andre selskaper og virksomheter, herunder deltagelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
▼ −8093 %
Equity
NOK 1.3m
▲ +205 %
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
13.09
Very good
Current assets ÷ current liabilities
Profitability
135.0%
Very good
Return on total assets
Solidity
98.6%
Very good
Equity as a share of total capital

Who owns JUR HOLDING AS?

JUR HOLDING AS
NOK 0 rev. · NOK −38,000 profit

JUR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JUR HOLDING AS own?

JUR HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JUR HOLDING AS

Who owns JUR HOLDING AS?

Evgenijus Jurinas is the largest registered owner, with 100.0%.

What is the revenue of JUR HOLDING AS?

JUR HOLDING AS had revenue of NOK 0 in 2025.

Where is JUR HOLDING AS based?

JUR HOLDING AS has its business address in Oltedal.

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.