biztrac. BETA
COMPANY REGISTER PROFILE
830716432 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HELGÅ HOLDING AS

Org. no. 830716432 Limited company (AS) Nesna Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 395,000
Operating profit NOK 230,000
Equity NOK 4.8m
Incorporated 2023
Share capital NOK 30,000

HELGÅ HOLDING AS is registered as a limited company in Nesna, Nordland with organisation number 830716432. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og leie ut fast eiendom og eie aksjer i og investere i andre selskaper og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 395,000 in revenue and NOK 230,000 in operating profit.

Key figures · 2025

Revenue
NOK 395,000
Operating profit
NOK 230,000
▲ +12430 %
Equity
NOK 4.8m
▲ +438 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
93.07
Very good
Current assets ÷ current liabilities
Profitability
79.7%
Very good
Return on total assets
Solidity
52.8%
Very good
Equity as a share of total capital

Who owns HELGÅ HOLDING AS?

HELGÅ HOLDING AS
NOK 395,000 rev. · NOK 230,000 profit

HELGÅ HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HELGÅ HOLDING AS own?

HELGÅ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HELGÅ HOLDING AS

Who owns HELGÅ HOLDING AS?

Ørjan Helgå is the largest registered owner, with 50.0%.

What is the revenue of HELGÅ HOLDING AS?

HELGÅ HOLDING AS had revenue of NOK 395,000 in 2025.

Where is HELGÅ HOLDING AS based?

HELGÅ HOLDING AS has its business address in Nesna.

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.