BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

LUMIT AS

Org. no. 912155552 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 566,000
Operating profit NOK 87,000
Equity NOK 141,000
Incorporated 2013
Share capital NOK 30,000

LUMIT AS is registered as a limited company in Asker, Akershus with organisation number 912155552. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Belysningsrådgivning for svaksynte og eldre. Utforming av belysningsløsninger i offentlige bygg. Salg og import av lysarmaturer, solavskjerming og It-løsninger. Utvikling og design av It-løsninger og lysarmaturer. Tilrettelegging av en helhetlig god løsning.”. The most recent filed accounts, for the 2024 financial year, show NOK 566,000 in revenue and NOK 87,000 in operating profit.

Key figures · 2024

Revenue
NOK 566,000
Operating profit
NOK 87,000
Equity
NOK 141,000
Est. value
NOK 502,000

Financial health · 2024

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

Who owns LUMIT AS?

PETER ØIVIND CARLSEN
LUMIT AS
NOK 566,000 rev. · NOK 87,000 profit

LUMIT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUMIT AS

Who owns LUMIT AS?

PETER ØIVIND CARLSEN is the largest registered owner, with 50.0%.

What is the revenue of LUMIT AS?

LUMIT AS had revenue of NOK 566,000 in 2024.

Who is the general manager of LUMIT AS?

Peter Øivind Carlsen is registered as general manager of LUMIT AS.

Where is LUMIT AS based?

LUMIT AS has its business address in Røyken.

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.