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

JORDET ELEKTRO AS

Org. no. 989368737 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 18.2m
Operating profit NOK 2.9m
Equity NOK 4.0m
Incorporated 2006
Employees 15
Share capital NOK 100,000

JORDET ELEKTRO AS is registered as a limited company in Oslo, Oslo with organisation number 989368737. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2006 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Elektrisk installasjonsarbeid, samt derved forbunden virksomhet, herunder å drive handel og å delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.2m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 18.2m
▲ +96 %
Operating profit
NOK 2.9m
▲ +148 %
Equity
NOK 4.0m
▲ +25 %
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
2.24
Very good
Current assets ÷ current liabilities
Profitability
49.1%
Very good
Return on total assets
Solidity
56.6%
Very good
Equity as a share of total capital

Who owns JORDET ELEKTRO AS?

JORDET ELEKTRO AS
NOK 18.2m rev. · NOK 2.9m profit

JORDET ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDET ELEKTRO AS

Who owns JORDET ELEKTRO AS?

Odd-Erik Jordet is the largest registered owner, with 100.0%.

What is the revenue of JORDET ELEKTRO AS?

JORDET ELEKTRO AS had revenue of NOK 18.2m in 2025.

Who is the general manager of JORDET ELEKTRO AS?

Odd-Erik Jordet is registered as general manager of JORDET ELEKTRO AS.

Where is JORDET ELEKTRO AS based?

JORDET ELEKTRO AS has its business address in Oslo.

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.