biztrac. BETA
COMPANY REGISTER PROFILE
934199758 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SHIVA AS

Org. no. 934199758 Limited company (AS) Gloppen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK −10,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

SHIVA AS is registered as a limited company in Gloppen, Vestland with organisation number 934199758. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet og andre produkter/tjenester som naturlig hører sammen med, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. 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
▲ +84 %
Equity
NOK −10,000
▼ −113 %

Financial health · 2025

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

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

Who owns SHIVA AS?

SHIVA AS
NOK 0 rev. · NOK −6,000 profit

SHIVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHIVA AS

Who owns SHIVA AS?

Jan Wiggo Rygg is the largest registered owner, with 100.0%.

What is the revenue of SHIVA AS?

SHIVA AS had revenue of NOK 0 in 2025.

Where is SHIVA AS based?

SHIVA AS has its business address in Sandane.

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.