BIZTRAC BETA
Business and other management consultancy activities

AL CONSULTING AS

Org. no. 986639446 Limited company (AS) Høyanger Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −41,000
Equity NOK 2.0m
Incorporated 2004
Share capital NOK 100,000

Signals

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

AL CONSULTING AS is registered as a limited company in Høyanger, Vestland with organisation number 986639446. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet med rådgivning vedrørende forvaltning av maskiner og utstyr samt alt som hermed står i forbindelse, herunder deltagelse i andre selskaper med lignenede formål. Videre inngår i selskapets formål investeringsvirksomhet og eiendomsvirksomhet.”.

Key figures · 2025

Operating profit
NOK −41,000
Equity
NOK 2.0m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns AL CONSULTING AS?

ASBJØRN LEIF LID
AL CONSULTING AS
· NOK −41,000 profit

AL CONSULTING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does AL CONSULTING AS own?

AL CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AL CONSULTING AS

Who owns AL CONSULTING AS?

ASBJØRN LEIF LID is the largest registered owner, with 45.0%.

Who is the general manager of AL CONSULTING AS?

Asbjørn Leif Lid is registered as general manager of AL CONSULTING AS.

Where is AL CONSULTING AS based?

AL CONSULTING AS has its business address in Kyrkjebø.

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.