BIZTRAC BETA
Construction of residential and non-residential buildings

LTT PROPERTY AS

Org. no. 926364529 Limited company (AS) Porsgrunn Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK −168,000
Incorporated 2020
Share capital NOK 120,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−168k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

LTT PROPERTY AS is registered as a limited company in Porsgrunn, Telemark with organisation number 926364529. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 120,000, divided into 30 shares. The company's stated purpose is: “Eiendomsselskap. Selskapet kan drive med kjøp, salg, utvikling, utleie, samt drift av fast eiendom. Konsulentvirksomhet innen byggebransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK −168,000

Financial health · 2024

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

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

Who owns LTT PROPERTY AS?

KHANG INVEST AS
LTT PROPERTY AS
NOK 0 rev. · NOK −24,000 profit

LTT PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LTT PROPERTY AS

Who owns LTT PROPERTY AS?

KHANG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LTT PROPERTY AS?

LTT PROPERTY AS had revenue of NOK 0 in 2024.

Where is LTT PROPERTY AS based?

LTT PROPERTY AS has its business address in Porsgrunn.

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.