BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

SOLAR HARVEST AS

Org. no. 993971685 Limited company (AS) Sola Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 2.4m
Incorporated 2009
Share capital NOK 101,000

SOLAR HARVEST AS is registered as a limited company in Sola, Rogaland with organisation number 993971685. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2009. Registered share capital is NOK 101,000, divided into 10109819 shares. The company's stated purpose is: “Investere og utøve aktivt eierskap i andre selskaper innenfor fornybar energi og matproduksjon, samt utvikle produkter og tjenester i tilknytning til dette. Salg av konsulenttjenester innenfor ansattes kompetanseområde.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 2.4m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.7%
Very good
Equity as a share of total capital

Who owns SOLAR HARVEST AS?

HELVIG INVEST AS
SOLAR HARVEST AS
NOK 0 rev. · NOK 0 profit

SOLAR HARVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SOLAR HARVEST AS own?

SOLAR HARVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLAR HARVEST AS

Who owns SOLAR HARVEST AS?

HELVIG INVEST AS is the largest registered owner, with 49.5%.

What is the revenue of SOLAR HARVEST AS?

SOLAR HARVEST AS had revenue of NOK 0 in 2024.

Where is SOLAR HARVEST AS based?

SOLAR HARVEST AS has its business address in Sola.

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.