BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

ALU-CONSULT BUR AS

Org. no. 995884011 Limited company (AS) Ringsaker Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 202,000
Equity NOK 193,000
Incorporated 2010
Share capital NOK 400,000

ALU-CONSULT BUR AS is registered as a limited company in Ringsaker, Innlandet with organisation number 995884011. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 2010. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Utvikling og salg av bur til dyr, handel med varer og tjenester, import og export, utlån av ledig kapital, og deltagelse i selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 202,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 202,000
Equity
NOK 193,000
Est. value
NOK 809,000

Financial health · 2024

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns ALU-CONSULT BUR AS?

KENT LASSE BIRKELAND
ALU-CONSULT BUR AS
NOK 2.2m rev. · NOK 202,000 profit

ALU-CONSULT BUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALU-CONSULT BUR AS

Who owns ALU-CONSULT BUR AS?

KENT LASSE BIRKELAND is the largest registered owner, with 100.0%.

What is the revenue of ALU-CONSULT BUR AS?

ALU-CONSULT BUR AS had revenue of NOK 2.2m in 2024.

Who is the general manager of ALU-CONSULT BUR AS?

Kent Lasse Birkeland is registered as general manager of ALU-CONSULT BUR AS.

Where is ALU-CONSULT BUR AS based?

ALU-CONSULT BUR AS has its business address in Brøttum.

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.