BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

LUMICO AS

Org. no. 923775560 Limited company (AS) Klepp Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 9,000
Equity NOK 115,000
Incorporated 2019
Share capital NOK 31,000

LUMICO AS is registered as a limited company in Klepp, Rogaland with organisation number 923775560. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2019. Registered share capital is NOK 31,000, divided into 990 shares. The company's stated purpose is: “Import og salg av byggematerialer og montering av diverse innen bygg og anlegg og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 9,000
Equity
NOK 115,000
Est. value
NOK 94,000

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.6%
Weak
Equity as a share of total capital

Who owns LUMICO AS?

ALEKSEI TRETJAKOV
LUMICO AS
NOK 6.7m rev. · NOK 9,000 profit

LUMICO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUMICO AS

Who owns LUMICO AS?

ALEKSEI TRETJAKOV is the largest registered owner, with 100.0%.

What is the revenue of LUMICO AS?

LUMICO AS had revenue of NOK 6.7m in 2025.

Who is the general manager of LUMICO AS?

Aleksei Tretjakov is registered as general manager of LUMICO AS.

Where is LUMICO AS based?

LUMICO AS has its business address in Klepp Stasjon.

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.