BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

JØRGENSENS SMIE AS

Org. no. 998529433 Limited company (AS) Ullensaker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 527,000
Operating profit NOK 46,000
Equity NOK 1.1m
Incorporated 2012
Share capital NOK 100,000

JØRGENSENS SMIE AS is registered as a limited company in Ullensaker, Akershus with organisation number 998529433. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av mekanisk verksted og alt som står i naturlig forbindelse med dette. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 527,000 in revenue and NOK 46,000 in operating profit.

Key figures · 2025

Revenue
NOK 527,000
Operating profit
NOK 46,000
Equity
NOK 1.1m
Est. value
NOK 826,000

Financial health · 2025

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

Who owns JØRGENSENS SMIE AS?

EIVIND JØRGENSEN
JØRGENSENS SMIE AS
NOK 527,000 rev. · NOK 46,000 profit

JØRGENSENS SMIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JØRGENSENS SMIE AS

Who owns JØRGENSENS SMIE AS?

EIVIND JØRGENSEN is the largest registered owner, with 100.0%.

What is the revenue of JØRGENSENS SMIE AS?

JØRGENSENS SMIE AS had revenue of NOK 527,000 in 2025.

Who is the general manager of JØRGENSENS SMIE AS?

Eivind Jørgensen is registered as general manager of JØRGENSENS SMIE AS.

Where is JØRGENSENS SMIE AS based?

JØRGENSENS SMIE AS has its business address in Kløfta.

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.