BIZTRAC BETA
Electrical installation

AGDER ELEKTRO AS

Org. no. 911780682 Limited company (AS) Lillesand Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −92,000
Equity NOK 2.9m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−92k kr).

AGDER ELEKTRO AS is registered as a limited company in Lillesand, Agder with organisation number 911780682. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive håndtverk, handel og kontroll innenfor elektrisk installasjon samt kjøp og salg av aksjer og eiendommer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −92,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −92,000
Equity
NOK 2.9m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns AGDER ELEKTRO AS?

ARNT HARRY LØNNBERG
AGDER ELEKTRO AS
NOK 4,000 rev. · NOK −92,000 profit

AGDER ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AGDER ELEKTRO AS own?

AGDER ELEKTRO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AGDER ELEKTRO AS

Who owns AGDER ELEKTRO AS?

ARNT HARRY LØNNBERG is the largest registered owner, with 100.0%.

What is the revenue of AGDER ELEKTRO AS?

AGDER ELEKTRO AS had revenue of NOK 4,000 in 2025.

Where is AGDER ELEKTRO AS based?

AGDER ELEKTRO AS has its business address in Lillesand.

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.