BIZTRAC BETA
Rental and operating of own or leased real estate

AKSIAL AS

Org. no. 933720942 Limited company (AS) Stord Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 8,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AKSIAL AS is registered as a limited company in Stord, Vestland with organisation number 933720942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 150000 shares. The company's stated purpose is: “Investerings- og forvaltningsverksemd, herunder deltaking i andre selskap, kjøp av aksjar og andre selskapsdelar, samt kjøp og drift av fast eigedom, samt all tilhøyrande verksemd.”.

Key figures · 2024

Operating profit
NOK −22,000
Equity
NOK 8,000
Est. value
NOK 8,000

Financial health · 2024

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

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

Who owns AKSIAL AS?

I HOLDING AS
AKSIAL AS
· NOK −22,000 profit

AKSIAL AS has 3 registered shareholders:

All shareholders and roles →

Which companies does AKSIAL AS own?

AKSIAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AKSIAL AS

Who owns AKSIAL AS?

I HOLDING AS is the largest registered owner, with 33.3%.

Who is the general manager of AKSIAL AS?

Ørjan Buchvold is registered as general manager of AKSIAL AS.

Where is AKSIAL AS based?

AKSIAL AS has its business address in Stord.

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.