BIZTRAC BETA
Repair and maintenance of personal and household goods n.e.c.

FLEXI SYSTUE AS

Org. no. 918345760 Limited company (AS) Lørenskog Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −44,000
Equity NOK 275,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

FLEXI SYSTUE AS is registered as a limited company in Lørenskog, Akershus with organisation number 918345760. The business is classified under repair and maintenance of personal and household goods n.e.c. (NACE 95.290). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Systua herunder reparasjon og forandring av klær, herunder delta i liknede og hvilken som helst virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −44,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −44,000
Equity
NOK 275,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
2.07
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.7%
Very good
Equity as a share of total capital

Who owns FLEXI SYSTUE AS?

HUNG NGUYEN
FLEXI SYSTUE AS
NOK 1.8m rev. · NOK −44,000 profit

FLEXI SYSTUE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLEXI SYSTUE AS

Who owns FLEXI SYSTUE AS?

HUNG NGUYEN is the largest registered owner, with 100.0%.

What is the revenue of FLEXI SYSTUE AS?

FLEXI SYSTUE AS had revenue of NOK 1.8m in 2024.

Who is the general manager of FLEXI SYSTUE AS?

Hung Nguyen is registered as general manager of FLEXI SYSTUE AS.

Where is FLEXI SYSTUE AS based?

FLEXI SYSTUE AS has its business address in Lørenskog.

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.