BIZTRAC BETA
COMPANY REGISTER PROFILE
928007936 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

HELIOS VISION AS

Org. no. 928007936 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −56,000
Equity NOK 56,000
Incorporated 2021
Share capital NOK 81,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).

HELIOS VISION AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928007936. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 81,000, divided into 27000 shares. The company's stated purpose is: “Eie underliggende selskaper innenfor teknologi. Selskapet har mulighet til å ha eksponering innenfor andre sektorer hvis det måtte ønske. Selskapet kan også tilby salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −56,000
Equity
NOK 56,000
Est. value
NOK 65,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns HELIOS VISION AS?

HELIOS VISION AS
NOK 0 rev. · NOK −56,000 profit

HELIOS VISION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELIOS VISION AS

Who owns HELIOS VISION AS?

ALEXANDER MØRCH-JENSEN is the largest registered owner, with 100.0%.

What is the revenue of HELIOS VISION AS?

HELIOS VISION AS had revenue of NOK 0 in 2025.

Where is HELIOS VISION AS based?

HELIOS VISION AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.