BIZTRAC BETA
Construction of residential and non-residential buildings

JURASVIST AS

Org. no. 818345062 Limited company (AS) Gulen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK −35,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−35k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

JURASVIST AS is registered as a limited company in Gulen, Vestland with organisation number 818345062. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tømrerarbeid samt kjøp og salg av byggevarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK −35,000

Financial health · 2024

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

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

Who owns JURASVIST AS?

JURIJUS SVISTUNAS
JURASVIST AS
NOK 0 rev. · NOK −30,000 profit

JURASVIST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JURASVIST AS

Who owns JURASVIST AS?

JURIJUS SVISTUNAS is the largest registered owner, with 100.0%.

What is the revenue of JURASVIST AS?

JURASVIST AS had revenue of NOK 0 in 2024.

Who is the general manager of JURASVIST AS?

Jurijus Svistunas is registered as general manager of JURASVIST AS.

Where is JURASVIST AS based?

JURASVIST AS has its business address in Eivindvik.

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.