BIZTRAC BETA
Manufacture of outerwear

NGUYEN SØM AS

Org. no. 933996611 Limited company (AS) Rælingen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 321,000
Operating profit NOK −21,000
Equity NOK −17,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−17k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

NGUYEN SØM AS is registered as a limited company in Rælingen, Akershus with organisation number 933996611. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Brodere bunadskjorter og montering av bunader. Også annen type søm.”. The most recent filed accounts, for the 2025 financial year, show NOK 321,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 321,000
Operating profit
NOK −21,000
Equity
NOK −17,000

Financial health · 2025

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

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

Who owns NGUYEN SØM AS?

Luu Thi Nguyen
NGUYEN SØM AS
NOK 321,000 rev. · NOK −21,000 profit

NGUYEN SØM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NGUYEN SØM AS

Who owns NGUYEN SØM AS?

Luu Thi Nguyen is the largest registered owner, with 100.0%.

What is the revenue of NGUYEN SØM AS?

NGUYEN SØM AS had revenue of NOK 321,000 in 2025.

Who is the general manager of NGUYEN SØM AS?

Luu Thi Nguyen is registered as general manager of NGUYEN SØM AS.

Where is NGUYEN SØM AS based?

NGUYEN SØM AS has its business address in Løvenstad.

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.