BIZTRAC BETA
Electrical installation

PRINCESS INVEST AS

Org. no. 933413470 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

PRINCESS INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 933413470. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering, utvikling, utleie og drift av fast eiendom. Elektro virksomhet, kjøp og salg elektriker.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 15,000
Est. value
NOK 15,000

Financial health · 2024

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

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

Who owns PRINCESS INVEST AS?

MINH PHUOC NGUYEN
PRINCESS INVEST AS
NOK 0 rev. · NOK −10,000 profit

PRINCESS INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRINCESS INVEST AS

Who owns PRINCESS INVEST AS?

MINH PHUOC NGUYEN is the largest registered owner, with 50.0%.

What is the revenue of PRINCESS INVEST AS?

PRINCESS INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of PRINCESS INVEST AS?

Thi Ky Von Vo is registered as general manager of PRINCESS INVEST AS.

Where is PRINCESS INVEST AS based?

PRINCESS INVEST AS has its business address in Fetsund.

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.