BIZTRAC BETA
Activities of advertising agencies

LUXHURRAY AS

Org. no. 927454300 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 647,000
Operating profit NOK −287,000
Equity NOK −553,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−553k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−287k kr).

LUXHURRAY AS is registered as a limited company in Oslo, Oslo with organisation number 927454300. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 760000 shares. The company's stated purpose is: “Drive med distribusjon av tekstilvarer og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 647,000 in revenue and NOK −287,000 in operating profit.

Key figures · 2025

Revenue
NOK 647,000
Operating profit
NOK −287,000
Equity
NOK −553,000

Financial health · 2025

Liquidity
5.02
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-39.1%
Weak
Equity as a share of total capital

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

Who owns LUXHURRAY AS?

MTC HOLDING AS
LUXHURRAY AS
NOK 647,000 rev. · NOK −287,000 profit

LUXHURRAY AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUXHURRAY AS

Who owns LUXHURRAY AS?

MTC HOLDING AS is the largest registered owner, with 46.1%.

What is the revenue of LUXHURRAY AS?

LUXHURRAY AS had revenue of NOK 647,000 in 2025.

Who is the general manager of LUXHURRAY AS?

David Strømman Nedal is registered as general manager of LUXHURRAY AS.

Where is LUXHURRAY AS based?

LUXHURRAY 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.