BIZTRAC BETA
Other technical consultancy

LUMUS AS

Org. no. 919441259 Limited company (AS) Ålesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 15,000
Operating profit NOK 11,000
Equity NOK −73,000
Incorporated 2017
Share capital NOK 40,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−73k kr).

LUMUS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 919441259. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Å drive teknoligisk virksomhet som kontroll, overvåkingssystemer, sikkerhetssystemer, og utstyr til offentlige og private bedrifter/organisasjoner og tilknyttede områder. Selskapet kan delta i og eie andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 15,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 15,000
Operating profit
NOK 11,000
Equity
NOK −73,000
Est. value
NOK 43,000

Financial health · 2024

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-39.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LUMUS AS?

MAGNE HARALD ÅKRE
LUMUS AS
NOK 15,000 rev. · NOK 11,000 profit

LUMUS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUMUS AS

Who owns LUMUS AS?

MAGNE HARALD ÅKRE is the largest registered owner, with 25.0%.

What is the revenue of LUMUS AS?

LUMUS AS had revenue of NOK 15,000 in 2024.

Who is the general manager of LUMUS AS?

Yrjan Stave Klokk is registered as general manager of LUMUS AS.

Where is LUMUS AS based?

LUMUS AS has its business address in Ålesund.

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.