biztrac. BETA
COMPANY REGISTER PROFILE
985729573 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of textiles

LILENG AS

Org. no. 985729573 Limited company (AS) Harstad Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK −352,000
Equity NOK 2.9m
Incorporated 2003
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−352k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LILENG AS is registered as a limited company in Harstad, Troms with organisation number 985729573. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2003. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Salg av interiørtekstiler og avskjerming.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK −352,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
▲ +74 %
Operating profit
NOK −352,000
▼ −733 %
Equity
NOK 2.9m
▼ −10 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
2.60
Very good
Current assets ÷ current liabilities
Profitability
-9.6%
Not satisfactory
Return on total assets
Solidity
80.7%
Very good
Equity as a share of total capital

Who owns LILENG AS?

LILENG AS
NOK 6.3m rev. · NOK −352,000 profit

LILENG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILENG AS

Who owns LILENG AS?

Tornerose AS is the largest registered owner, with 100.0%.

What is the revenue of LILENG AS?

LILENG AS had revenue of NOK 6.3m in 2025.

Who is the general manager of LILENG AS?

Lars Ivar Lileng is registered as general manager of LILENG AS.

Where is LILENG AS based?

LILENG AS has its business address in Harstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.