BIZTRAC BETA
Industrial product and fashion design activities

SUNAQ AS

Org. no. 933219194 Limited company (AS) Ørsta Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 230,000
Operating profit NOK −204,000
Equity NOK −179,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−179k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−204k kr).

SUNAQ AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 933219194. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Teknisk konsulentvirksomhet og annen energihandel, samt øvrig verksemd som hermed står i sammenheng.”. The most recent filed accounts, for the 2024 financial year, show NOK 230,000 in revenue and NOK −204,000 in operating profit.

Key figures · 2024

Revenue
NOK 230,000
Operating profit
NOK −204,000
Equity
NOK −179,000

Financial health · 2024

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

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

Who owns SUNAQ AS?

SUNAQ HOLDING AS
SUNAQ AS
NOK 230,000 rev. · NOK −204,000 profit

SUNAQ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUNAQ AS

Who owns SUNAQ AS?

SUNAQ HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SUNAQ AS?

SUNAQ AS had revenue of NOK 230,000 in 2024.

Who is the general manager of SUNAQ AS?

Geir Arne Aarseth is registered as general manager of SUNAQ AS.

Where is SUNAQ AS based?

SUNAQ AS has its business address in Ørsta.

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.