BIZTRAC BETA
Electrical installation

MEMO ELEKTRO KOMMUNIKASJON AS

Org. no. 996138259 Limited company (AS) Lørenskog Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 333,000
Equity NOK 1.2m
Incorporated 2010
Share capital NOK 100,000

MEMO ELEKTRO KOMMUNIKASJON AS is registered as a limited company in Lørenskog, Akershus with organisation number 996138259. 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, virksomhet direkte i tilknytning til dette samt deltakelse i andre selskaper. ”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 333,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 333,000
Equity
NOK 1.2m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
4.85
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.3%
Very good
Equity as a share of total capital

Who owns MEMO ELEKTRO KOMMUNIKASJON AS?

JØRN IVAR PEDERSEN
MEMO ELEKTRO KOMMUNIKASJON AS
NOK 1.4m rev. · NOK 333,000 profit

MEMO ELEKTRO KOMMUNIKASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEMO ELEKTRO KOMMUNIKASJON AS

Who owns MEMO ELEKTRO KOMMUNIKASJON AS?

JØRN IVAR PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of MEMO ELEKTRO KOMMUNIKASJON AS?

MEMO ELEKTRO KOMMUNIKASJON AS had revenue of NOK 1.4m in 2025.

Who is the general manager of MEMO ELEKTRO KOMMUNIKASJON AS?

Jørn Ivar Pedersen is registered as general manager of MEMO ELEKTRO KOMMUNIKASJON AS.

Where is MEMO ELEKTRO KOMMUNIKASJON AS based?

MEMO ELEKTRO KOMMUNIKASJON AS has its business address in Lørenskog.

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.