BIZTRAC BETA
Retail sale of clothing

MATCHLESS LIVING AS

Org. no. 824676682 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −49,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

MATCHLESS LIVING AS is registered as a limited company in Bærum, Akershus with organisation number 824676682. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer, utvikling av konsument og merkevarer, samt annen tilsvarende virksomhet, samt alt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −49,000

Financial health · 2025

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

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

Who owns MATCHLESS LIVING AS?

MATHIAS CHRISTOFER HOLST
MATCHLESS LIVING AS
NOK 0 rev. · NOK 0 profit

MATCHLESS LIVING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MATCHLESS LIVING AS

Who owns MATCHLESS LIVING AS?

MATHIAS CHRISTOFER HOLST is the largest registered owner, with 80.0%.

What is the revenue of MATCHLESS LIVING AS?

MATCHLESS LIVING AS had revenue of NOK 0 in 2024.

Who is the general manager of MATCHLESS LIVING AS?

Mathias Christofer Holst is registered as general manager of MATCHLESS LIVING AS.

Where is MATCHLESS LIVING AS based?

MATCHLESS LIVING AS has its business address in Jar.

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.