biztrac. BETA
COMPANY REGISTER PROFILE
928305988 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Machining of metals

AVCLL HOLDING AS

Org. no. 928305988 Limited company (AS) Vågan Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −59,000
Equity NOK 3.2m
Incorporated 2021
Share capital NOK 30,000

Signals

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

AVCLL HOLDING AS is registered as a limited company in Vågan, Nordland with organisation number 928305988. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −59,000
▲ +25 %
Equity
NOK 3.2m
▲ +1697 %
Est. value
NOK 21.5m

Financial health · 2025

Liquidity
2.92
Very good
Current assets ÷ current liabilities
Profitability
53.5%
Very good
Return on total assets
Solidity
27.5%
Good
Equity as a share of total capital

Who owns AVCLL HOLDING AS?

AVCLL HOLDING AS
· NOK −59,000 profit

AVCLL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AVCLL HOLDING AS own?

AVCLL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AVCLL HOLDING AS

Who owns AVCLL HOLDING AS?

Christian Aleksander Bye is the largest registered owner, with 100.0%.

Where is AVCLL HOLDING AS based?

AVCLL HOLDING AS has its business address in Kabelvåg.

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

Report a problem

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