BIZTRAC BETA
Rental and operating of own or leased real estate

TLS MUR EIENDOM AS

Org. no. 932453347 Limited company (AS) Lyngdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 240,000
Operating profit NOK 125,000
Equity NOK 102,000
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TLS MUR EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 932453347. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å eie, utvikle, kjøpe og selge tomt for utbygging, oppføring av bygg for salg og utleie samt alt hva her hører til. Selskapet kan også delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 240,000 in revenue and NOK 125,000 in operating profit.

Key figures · 2024

Revenue
NOK 240,000
Operating profit
NOK 125,000
Equity
NOK 102,000
Est. value
NOK 110,000

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.9%
Weak
Equity as a share of total capital

Who owns TLS MUR EIENDOM AS?

TLS MUR AS
TLS MUR EIENDOM AS
NOK 240,000 rev. · NOK 125,000 profit

TLS MUR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TLS MUR EIENDOM AS

Who owns TLS MUR EIENDOM AS?

TLS MUR AS is the largest registered owner, with 100.0%.

What is the revenue of TLS MUR EIENDOM AS?

TLS MUR EIENDOM AS had revenue of NOK 240,000 in 2024.

Where is TLS MUR EIENDOM AS based?

TLS MUR EIENDOM AS has its business address in Lyngdal.

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.