BIZTRAC BETA
Electrical installation

RM ELEKTRO AS

Org. no. 995166666 Limited company (AS) Ål Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 262,000
Operating profit NOK −36,000
Equity NOK −318,000
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−318k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−36k kr).

RM ELEKTRO AS is registered as a limited company in Ål, Buskerud with organisation number 995166666. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Elektroinstallasjon og salg av elektrisk materiell/utstyr, samt annen virksomhet som står i naturlig forbindelse med hovedformålet.”. The most recent filed accounts, for the 2024 financial year, show NOK 262,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 262,000
Operating profit
NOK −36,000
Equity
NOK −318,000

Financial health · 2024

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

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

Who owns RM ELEKTRO AS?

Rune Mølster
RM ELEKTRO AS
NOK 262,000 rev. · NOK −36,000 profit

RM ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RM ELEKTRO AS

Who owns RM ELEKTRO AS?

Rune Mølster is the largest registered owner, with 100.0%.

What is the revenue of RM ELEKTRO AS?

RM ELEKTRO AS had revenue of NOK 262,000 in 2024.

Who is the general manager of RM ELEKTRO AS?

Rune Mølster is registered as general manager of RM ELEKTRO AS.

Where is RM ELEKTRO AS based?

RM ELEKTRO AS has its business address in Ål.

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.