BIZTRAC BETA
Uoppgitt

AISUN HOLDING AS

Org. no. 924681128 Limited company (AS) Hitra Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 760,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

AISUN HOLDING AS is registered as a limited company in Hitra, Trøndelag with organisation number 924681128. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Være et holdingselskap, og med det drive med kjøp og salg av aksjer, samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 760,000
Est. value
NOK 864,000

Financial health · 2025

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

Who owns AISUN HOLDING AS?

AINA SUNDET
AISUN HOLDING AS
NOK 0 rev. · NOK −1,000 profit

AISUN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AISUN HOLDING AS own?

AISUN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AISUN HOLDING AS

Who owns AISUN HOLDING AS?

AINA SUNDET is the largest registered owner, with 100.0%.

What is the revenue of AISUN HOLDING AS?

AISUN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of AISUN HOLDING AS?

Aina Sundet is registered as general manager of AISUN HOLDING AS.

Where is AISUN HOLDING AS based?

AISUN HOLDING AS has its business address in Sandstad.

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.