BIZTRAC BETA
Other building completion and finishing

LUMON NORGE AS

Org. no. 981888863 Limited company (AS) Lillestrøm Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 48.0m
Operating profit NOK −7.9m
Equity NOK 2.5m
Incorporated 2000
Employees 21
Share capital NOK 850,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,9 mill kr).

LUMON NORGE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 981888863. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2000 and has 21 registered employees. Registered share capital is NOK 850,000, divided into 850 shares. The company's stated purpose is: “Byggevirksomhet innen glass og aluminium, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.0m in revenue and NOK −7.9m in operating profit.

Key figures · 2024

Revenue
NOK 48.0m
Operating profit
NOK −7.9m
Equity
NOK 2.5m
Est. value
NOK 17.8m

Financial health · 2024

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

Who owns LUMON NORGE AS?

LUMON INTERNATIONAL OY
LUMON NORGE AS
NOK 48.0m rev. · NOK −7.9m profit

LUMON NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUMON NORGE AS

Who owns LUMON NORGE AS?

LUMON INTERNATIONAL OY is the largest registered owner, with 100.0%.

What is the revenue of LUMON NORGE AS?

LUMON NORGE AS had revenue of NOK 48.0m in 2024.

Who is the general manager of LUMON NORGE AS?

Daniel Aaron Salomon Taskinen is registered as general manager of LUMON NORGE AS.

Where is LUMON NORGE AS based?

LUMON NORGE AS has its business address in Skjetten.

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.