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

SINGH PROPERTY AS

Org. no. 933944778 Limited company (AS) Tønsberg Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

SINGH PROPERTY AS is registered as a limited company in Tønsberg, Vestfold with organisation number 933944778. 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 30,000, divided into 3000 shares. The company's stated purpose is: “Investere, forvalte og formidle fast eiendom, samt hva hermed står i forbindelse med dette, herunder delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −4,000
Equity
NOK 15,000
Est. value
NOK 14,000

Financial health · 2024

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.4%
Weak
Equity as a share of total capital

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

Who owns SINGH PROPERTY AS?

LAKHVINDER SINGH SIDHU BRAR
SINGH PROPERTY AS
· NOK −4,000 profit

SINGH PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SINGH PROPERTY AS own?

SINGH PROPERTY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINGH PROPERTY AS

Who owns SINGH PROPERTY AS?

LAKHVINDER SINGH SIDHU BRAR is the largest registered owner, with 100.0%.

Who is the general manager of SINGH PROPERTY AS?

Lakhvinder Singh Sidhu Brar is registered as general manager of SINGH PROPERTY AS.

Where is SINGH PROPERTY AS based?

SINGH PROPERTY AS has its business address in Tønsberg.

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.