BIZTRAC BETA
Other real estate activities on a fee or contract basis

LUX HOTEL 2 AS

Org. no. 834625822 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 503,000
Operating profit NOK −1.4m
Equity NOK 4.6m
Incorporated 2024
Share capital NOK 480,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LUX HOTEL 2 AS is registered as a limited company in Lillestrøm, Akershus with organisation number 834625822. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2024. Registered share capital is NOK 480,000, divided into 4800 shares. The company's stated purpose is: “Eie og forvalt eiendommen LUX Hotel 2.”. The most recent filed accounts, for the 2024 financial year, show NOK 503,000 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 503,000
Operating profit
NOK −1.4m
Equity
NOK 4.6m
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
194.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns LUX HOTEL 2 AS?

TARALDSET HOLDING AS
LUX HOTEL 2 AS
NOK 503,000 rev. · NOK −1.4m profit

LUX HOTEL 2 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LUX HOTEL 2 AS er morselskap for 24 datterselskaper:

Frequently asked questions about LUX HOTEL 2 AS

Who owns LUX HOTEL 2 AS?

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

What is the revenue of LUX HOTEL 2 AS?

LUX HOTEL 2 AS had revenue of NOK 503,000 in 2024.

Where is LUX HOTEL 2 AS based?

LUX HOTEL 2 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.