BIZTRAC BETA
Manufacture of builders’ ware of plastic

LITEX AS

Org. no. 915050832 Limited company (AS) Sandefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 66.1m
Operating profit NOK −765,000
Equity NOK 15.0m
Incorporated 2015
Employees 14
Share capital NOK 30,000

Signals

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

LITEX AS is registered as a limited company in Sandefjord, Vestfold with organisation number 915050832. The business is classified under manufacture of builders’ ware of plastic (NACE 22.240). The company was incorporated in 2015 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Import, eksport, produksjon og detaljsalg av varer til byggebransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 66.1m in revenue and NOK −765,000 in operating profit.

Key figures · 2024

Revenue
NOK 66.1m
Operating profit
NOK −765,000
Equity
NOK 15.0m
Est. value
NOK 43.4m

Financial health · 2024

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

Who owns LITEX AS?

PROTAN AS
LITEX AS
NOK 66.1m rev. · NOK −765,000 profit

LITEX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LITEX AS

Who owns LITEX AS?

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

What is the revenue of LITEX AS?

LITEX AS had revenue of NOK 66.1m in 2024.

Who is the general manager of LITEX AS?

Frank Tungseth Utheim is registered as general manager of LITEX AS.

Where is LITEX AS based?

LITEX AS has its business address in Sandefjord.

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.