BIZTRAC BETA
Rental and leasing of air transport equipment

HELISCAN INVEST AS

Org. no. 990430357 Limited company (AS) Frosta Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 2.4m
Equity NOK 7.0m
Incorporated 2006
Share capital NOK 1.5m

Signals

1 flags
  • Nylig endring 2026-02-09 Adresseendring registrert 2026-02-09.

HELISCAN INVEST AS is registered as a limited company in Frosta, Trøndelag with organisation number 990430357. The business is classified under rental and leasing of air transport equipment (NACE 77.350). The company was incorporated in 2006. Registered share capital is NOK 1.5m, divided into 14850 shares. The company's stated purpose is: “Erverve, eie og forvalte luftfartøy, fast eiendom, anleggsmaskiner og kjøretøy, aksjer og øvrige verdipapirer, og virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 2.4m
Equity
NOK 7.0m
Est. value
NOK 9.3m

Financial health · 2024

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

Who owns HELISCAN INVEST AS?

GREENWAY AS
HELISCAN INVEST AS
NOK 8.1m rev. · NOK 2.4m profit

HELISCAN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELISCAN INVEST AS

Who owns HELISCAN INVEST AS?

GREENWAY AS is the largest registered owner, with 50.0%.

What is the revenue of HELISCAN INVEST AS?

HELISCAN INVEST AS had revenue of NOK 8.1m in 2024.

Who is the general manager of HELISCAN INVEST AS?

Arnt Erik Ring is registered as general manager of HELISCAN INVEST AS.

Where is HELISCAN INVEST AS based?

HELISCAN INVEST AS has its business address in Frosta.

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.