BIZTRAC BETA
Electrical installation

NESODDEN ELEKTRO AS

Org. no. 922944245 Limited company (AS) Nesodden Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK −188,000
Equity NOK 94,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−188k kr).

NESODDEN ELEKTRO AS is registered as a limited company in Nesodden, Akershus with organisation number 922944245. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utførelse av elektroinstallasjoner i hus og bygninger, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK −188,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK −188,000
Equity
NOK 94,000
Est. value
NOK 1.4m

Financial health · 2024

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

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

Who owns NESODDEN ELEKTRO AS?

RICHARD MARKI
NESODDEN ELEKTRO AS
NOK 4.0m rev. · NOK −188,000 profit

NESODDEN ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESODDEN ELEKTRO AS

Who owns NESODDEN ELEKTRO AS?

RICHARD MARKI is the largest registered owner, with 100.0%.

What is the revenue of NESODDEN ELEKTRO AS?

NESODDEN ELEKTRO AS had revenue of NOK 4.0m in 2024.

Who is the general manager of NESODDEN ELEKTRO AS?

Richard Marki is registered as general manager of NESODDEN ELEKTRO AS.

Where is NESODDEN ELEKTRO AS based?

NESODDEN ELEKTRO AS has its business address in Nesoddtangen.

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.