biztrac. BETA
COMPANY REGISTER PROFILE
935599296 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Manufacture of communication equipment

AVLABS HOLDING AS

Org. no. 935599296 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7
Equity NOK 38,000
Incorporated 2025
Share capital NOK 45,000

Signals

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

AVLABS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 935599296. The business is classified under manufacture of communication equipment (NACE 26.300). The company was incorporated in 2025. Registered share capital is NOK 45,000, divided into 45000 shares. The company's stated purpose is: “Investering i andre selskaper og andre tjenester som naturlig hører sammen med dette, herunder kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −7
Equity
NOK 38,000
Est. value
NOK 45,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 AVLABS HOLDING AS?

AVLABS HOLDING AS
· NOK −7 profit

AVLABS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AVLABS HOLDING AS own?

AVLABS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AVLABS HOLDING AS

Who owns AVLABS HOLDING AS?

MIKKMAKK AS is the largest registered owner, with 100.0%.

Where is AVLABS HOLDING AS based?

AVLABS HOLDING AS has its business address in Oslo.

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.