BIZTRAC BETA
Manufacture of other technical and industrial textiles

ELDI PROTECTION AS

Org. no. 994668420 Limited company (AS) Ørland Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 88.2m
Operating profit NOK 10.2m
Equity NOK 43.1m
Incorporated 2009
Employees 43
Share capital NOK 5.3m

ELDI PROTECTION AS is registered as a limited company in Ørland, Trøndelag with organisation number 994668420. The business is classified under manufacture of other technical and industrial textiles (NACE 13.960). The company was incorporated in 2009 and has 43 registered employees. Registered share capital is NOK 5.3m, divided into 3000000 shares. The company's stated purpose is: “Utvikling, produksjon og salg av produkter basert på industritekstiler og lignende materialer. Selskapet kan også investere i lignende selskapet hvis hensiktsmessig.”. The most recent filed accounts, for the 2025 financial year, show NOK 88.2m in revenue and NOK 10.2m in operating profit.

Key figures · 2025

Revenue
NOK 88.2m
Operating profit
NOK 10.2m
Equity
NOK 43.1m
Est. value
NOK 67.0m

Financial health · 2025

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

Who owns ELDI PROTECTION AS?

HAMPIÐJAN HF
ELDI PROTECTION AS
NOK 88.2m rev. · NOK 10.2m profit

ELDI PROTECTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELDI PROTECTION AS

Who owns ELDI PROTECTION AS?

HAMPIÐJAN HF is the largest registered owner, with 100.0%.

What is the revenue of ELDI PROTECTION AS?

ELDI PROTECTION AS had revenue of NOK 88.2m in 2025.

Who is the general manager of ELDI PROTECTION AS?

Tore Harsvik is registered as general manager of ELDI PROTECTION AS.

Where is ELDI PROTECTION AS based?

ELDI PROTECTION AS has its business address in Oksvoll.

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.