BIZTRAC BETA
Repair and maintenance of motor vehicles

BILMIX AS

Org. no. 918702741 Limited company (AS) Aurskog-Høland Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 121,000
Equity NOK 126,000
Incorporated 2017
Employees 7
Share capital NOK 30,000

BILMIX AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 918702741. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bilpleie og lakkering, salg av bruktbiler, import, salg og nettsalg av bildeler, samt dertil hørende virksomhet, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 121,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 121,000
Equity
NOK 126,000
Est. value
NOK 422,000

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.4%
Weak
Equity as a share of total capital

Who owns BILMIX AS?

LAISVUNAS VALUZIS
BILMIX AS
NOK 7.0m rev. · NOK 121,000 profit

BILMIX AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILMIX AS

Who owns BILMIX AS?

LAISVUNAS VALUZIS is the largest registered owner, with 50.0%.

What is the revenue of BILMIX AS?

BILMIX AS had revenue of NOK 7.0m in 2024.

Who is the general manager of BILMIX AS?

Laisvunas Valuzis is registered as general manager of BILMIX AS.

Where is BILMIX AS based?

BILMIX AS has its business address in Fosser.

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.