BIZTRAC BETA
COMPANY REGISTER PROFILE
914842735 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Machining of metals

ELFUEL AS

Org. no. 914842735 Limited company (AS) Etne Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 143,000
Operating profit NOK 55,000
Equity NOK −493,000
Incorporated 2015
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−493k kr).

ELFUEL AS is registered as a limited company in Etne, Vestland with organisation number 914842735. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utleie av arbeidskraft, samt bygging av bygg. Transport av materiell.”. The most recent filed accounts, for the 2025 financial year, show NOK 143,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 143,000
▼ −36 %
Operating profit
NOK 55,000
▲ +203 %
Equity
NOK −493,000
▼ −9 %
Est. value
NOK 102,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
148.7%
Very good
Return on total assets
Solidity
-3815.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ELFUEL AS?

ELFUEL AS
NOK 143,000 rev. · NOK 55,000 profit

ELFUEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELFUEL AS

Who owns ELFUEL AS?

SIGVE HJELMTVEIT JENSEN is the largest registered owner, with 100.0%.

What is the revenue of ELFUEL AS?

ELFUEL AS had revenue of NOK 143,000 in 2025.

Who is the general manager of ELFUEL AS?

Sigve Hjelmtveit Jensen is registered as general manager of ELFUEL AS.

Where is ELFUEL AS based?

ELFUEL AS has its business address in Etne.

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

Report a problem

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