BIZTRAC BETA
Hotels and similar accommodation

LUX DRIFT AS

Org. no. 931814850 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 847,000
Equity NOK 100,000
Incorporated 2023
Employees 9
Share capital NOK 100,000

LUX DRIFT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 931814850. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2023 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Drive med ulik drift av næringslokaler, som renhold, drift eiendom, driftstjenester hotel, restaurant, spa og andre nærliggende forretningsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 847,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 847,000
Equity
NOK 100,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns LUX DRIFT AS?

TARALDSET HOLDING AS
LUX DRIFT AS
NOK 3.4m rev. · NOK 847,000 profit

LUX DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LUX DRIFT AS er morselskap for 24 datterselskaper:

Frequently asked questions about LUX DRIFT AS

Who owns LUX DRIFT AS?

TARALDSET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LUX DRIFT AS?

LUX DRIFT AS had revenue of NOK 3.4m in 2024.

Who is the general manager of LUX DRIFT AS?

Yaroslav Medvedev-Taraldset is registered as general manager of LUX DRIFT AS.

Where is LUX DRIFT AS based?

LUX DRIFT AS has its business address in Lillestrøm.

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.