BIZTRAC BETA
Activities of tour guides

LUX TOURS AS

Org. no. 934159977 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 218,000
Operating profit NOK −11,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

LUX TOURS AS is registered as a limited company in Oslo, Oslo with organisation number 934159977. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen guiding og reiseleding 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 218,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 218,000
Operating profit
NOK −11,000
Equity
NOK 15,000
Est. value
NOK 145,000

Financial health · 2025

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.5%
Weak
Equity as a share of total capital

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

Who owns LUX TOURS AS?

XUEMEI CHEN
LUX TOURS AS
NOK 218,000 rev. · NOK −11,000 profit

LUX TOURS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUX TOURS AS

Who owns LUX TOURS AS?

XUEMEI CHEN is the largest registered owner, with 100.0%.

What is the revenue of LUX TOURS AS?

LUX TOURS AS had revenue of NOK 218,000 in 2025.

Who is the general manager of LUX TOURS AS?

Xuemei Chen is registered as general manager of LUX TOURS AS.

Where is LUX TOURS AS based?

LUX TOURS 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.