BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

LYXDEKK AS

Org. no. 998562481 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 501,000
Operating profit NOK 9,000
Equity NOK −10,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−10k kr).

LYXDEKK AS is registered as a limited company in Oslo, Oslo with organisation number 998562481. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Drive med salg av bildekk, bildeler og tjenester som hører til dekksalg, montering, balsansering, hjulskift og det som ellers høres til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 501,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 501,000
Operating profit
NOK 9,000
Equity
NOK −10,000
Est. value
NOK 46,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LYXDEKK AS?

DAGFINN LINDBOM
LYXDEKK AS
NOK 501,000 rev. · NOK 9,000 profit

LYXDEKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYXDEKK AS

Who owns LYXDEKK AS?

DAGFINN LINDBOM is the largest registered owner, with 50.0%.

What is the revenue of LYXDEKK AS?

LYXDEKK AS had revenue of NOK 501,000 in 2024.

Who is the general manager of LYXDEKK AS?

Dagfinn Lindbom is registered as general manager of LYXDEKK AS.

Where is LYXDEKK AS based?

LYXDEKK AS has its business address in Oslo.

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.