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

LILLIAN SYSTUE AS

Org. no. 920197191 Limited company (AS) Sandnes Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 496,000
Equity NOK 1.8m
Incorporated 2017
Employees 5
Share capital NOK 30,000

LILLIAN SYSTUE AS is registered as a limited company in Sandnes, Rogaland with organisation number 920197191. The business is classified under repair and maintenance of personal and household goods n.e.c. (NACE 95.290). The company was incorporated in 2017 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Systue, reparasjon og produksjon av tekstiler. Generell handelsvirksomhet. Deltakelse i andre selskaper. Undervisning innen området.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 496,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 496,000
Equity
NOK 1.8m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns LILLIAN SYSTUE AS?

HOA THANH THI HO
LILLIAN SYSTUE AS
NOK 2.5m rev. · NOK 496,000 profit

LILLIAN SYSTUE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLIAN SYSTUE AS

Who owns LILLIAN SYSTUE AS?

HOA THANH THI HO is the largest registered owner, with 100.0%.

What is the revenue of LILLIAN SYSTUE AS?

LILLIAN SYSTUE AS had revenue of NOK 2.5m in 2025.

Who is the general manager of LILLIAN SYSTUE AS?

Hoa Thanh Thi Ho is registered as general manager of LILLIAN SYSTUE AS.

Where is LILLIAN SYSTUE AS based?

LILLIAN SYSTUE AS has its business address in Sandnes.

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.