BIZTRAC BETA
COMPANY REGISTER PROFILE
928488918 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

AL-INVEST AS

Org. no. 928488918 Limited company (AS) Vennesla Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 112,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

AL-INVEST AS is registered as a limited company in Vennesla, Agder with organisation number 928488918. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringsvirksomhet i aksjer og andeler, samt hva dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −8,000
Equity
NOK 112,000
Est. value
NOK 15.6m

Financial health · 2025

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

Who owns AL-INVEST AS?

AL-INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AL-INVEST AS own?

AL-INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AL-INVEST AS

Who owns AL-INVEST AS?

ANDRÉ ANDERSEN is the largest registered owner, with 50.0%.

Where is AL-INVEST AS based?

AL-INVEST AS has its business address in Vennesla.

Property

Business address Bokfinkvegen 10, 4708 Vennesla
Cadastral unit 4223-4/355/0/0
Building Enebolig m/hybel/sokkelleil. · 3 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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