biztrac. BETA
COMPANY REGISTER PROFILE
930846953 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

EL-TJENESTER AS

Org. no. 930846953 Limited company (AS) Nord-Aurdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 339,000
Equity NOK 3.3m
Incorporated 2023
Share capital NOK 300,000

EL-TJENESTER AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 930846953. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2023. Registered share capital is NOK 300,000, divided into 120 shares. The company's stated purpose is: “Foreta elektriske installasjonsarbeider, selge el-artikler, kjærneboring, samt investering i aksjer, aksjefond og fast eiendom. Og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 339,000 in operating profit.

Former names: ELTJENESTER AS

Key figures · 2025

Revenue
NOK 9.4m
▲ +1 %
Operating profit
NOK 339,000
▼ −51 %
Equity
NOK 3.3m
▲ +10 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
2.30
Very good
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns EL-TJENESTER AS?

EL-TJENESTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EL-TJENESTER AS

Who owns EL-TJENESTER AS?

OLSDEILDE HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of EL-TJENESTER AS?

EL-TJENESTER AS had revenue of NOK 9.4m in 2025.

Who is the general manager of EL-TJENESTER AS?

Einar Ranheim is registered as general manager of EL-TJENESTER AS.

Where is EL-TJENESTER AS based?

EL-TJENESTER AS has its business address in Fagernes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.