BIZTRAC BETA
Uoppgitt

HIMALAYA HOLDING AS

Org. no. 922330697 Limited company (AS) Porsgrunn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −49,000
Equity NOK 664,000
Incorporated 2019
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−49k kr).

HIMALAYA HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 922330697. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −49,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −49,000
Equity
NOK 664,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns HIMALAYA HOLDING AS?

GLENN-ROBIN STOKKE GILL
HIMALAYA HOLDING AS
NOK 0 rev. · NOK −49,000 profit

HIMALAYA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HIMALAYA HOLDING AS own?

HIMALAYA HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HIMALAYA HOLDING AS

Who owns HIMALAYA HOLDING AS?

GLENN-ROBIN STOKKE GILL is the largest registered owner, with 100.0%.

What is the revenue of HIMALAYA HOLDING AS?

HIMALAYA HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of HIMALAYA HOLDING AS?

Hilde Stokke Gill is registered as general manager of HIMALAYA HOLDING AS.

Where is HIMALAYA HOLDING AS based?

HIMALAYA HOLDING AS has its business address in Porsgrunn.

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.