biztrac. BETA
COMPANY REGISTER PROFILE
934023587 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

AUTO LX AS

Org. no. 934023587 Limited company (AS) Kragerø Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 101,000
Equity NOK 115,000
Incorporated 2024
Share capital NOK 30,000

AUTO LX AS is registered as a limited company in Kragerø, Telemark with organisation number 934023587. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Selge varer og tjenester innen personbiler - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
▲ +1664 %
Operating profit
NOK 101,000
▲ +470 %
Equity
NOK 115,000
▲ +203 %
Est. value
NOK 401,000

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
20.9%
Very good
Return on total assets
Solidity
12.8%
Satisfactory
Equity as a share of total capital

Who owns AUTO LX AS?

AUTO LX AS
NOK 9.4m rev. · NOK 101,000 profit

AUTO LX AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AUTO LX AS er morselskap for 1 datterselskap:

Frequently asked questions about AUTO LX AS

Who owns AUTO LX AS?

LUX GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of AUTO LX AS?

AUTO LX AS had revenue of NOK 9.4m in 2025.

Who is the general manager of AUTO LX AS?

Kujtim Bytyqi is registered as general manager of AUTO LX AS.

Where is AUTO LX AS based?

AUTO LX AS has its business address in Kragerø.

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.