BIZTRAC BETA
Machining of metals

J.E SVEIS OG INDUSTRIRØR AS

Org. no. 912408426 Limited company (AS) Tinn Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 17,000
Equity NOK 100,000
Incorporated 2013
Share capital NOK 50,000

J.E SVEIS OG INDUSTRIRØR AS is registered as a limited company in Tinn, Telemark with organisation number 912408426. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Sveising, metallbearbeiding, industrirør og mekanisk arbeid, samt salg av varer og tjenester som naturlig faller sammen med dette. Deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 17,000
Equity
NOK 100,000
Est. value
NOK 106,000

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.3%
Satisfactory
Equity as a share of total capital

Who owns J.E SVEIS OG INDUSTRIRØR AS?

JOSTEIN ELNES
J.E SVEIS OG INDUSTRIRØR AS
NOK 1.7m rev. · NOK 17,000 profit

J.E SVEIS OG INDUSTRIRØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J.E SVEIS OG INDUSTRIRØR AS

Who owns J.E SVEIS OG INDUSTRIRØR AS?

JOSTEIN ELNES is the largest registered owner, with 100.0%.

What is the revenue of J.E SVEIS OG INDUSTRIRØR AS?

J.E SVEIS OG INDUSTRIRØR AS had revenue of NOK 1.7m in 2024.

Who is the general manager of J.E SVEIS OG INDUSTRIRØR AS?

Jostein Elnes is registered as general manager of J.E SVEIS OG INDUSTRIRØR AS.

Where is J.E SVEIS OG INDUSTRIRØR AS based?

J.E SVEIS OG INDUSTRIRØR AS has its business address in Miland.

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.