BIZTRAC BETA
Machining of metals

NORSK STANSEINDUSTRI AS

Org. no. 957968945 Limited company (AS) Lillestrøm Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 41.5m
Operating profit NOK 775,000
Equity NOK 6.4m
Incorporated 1990
Employees 16
Share capital NOK 948,000

NORSK STANSEINDUSTRI AS is registered as a limited company in Lillestrøm, Akershus with organisation number 957968945. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 1990 and has 16 registered employees. Registered share capital is NOK 948,000, divided into 60 shares. The company's stated purpose is: “Handel og industri og det som står i forbindelse med dette, herunder å være intressert med aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 41.5m in revenue and NOK 775,000 in operating profit.

Key figures · 2025

Revenue
NOK 41.5m
Operating profit
NOK 775,000
Equity
NOK 6.4m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns NORSK STANSEINDUSTRI AS?

ECKMANN HOLDING AS
NORSK STANSEINDUSTRI AS
NOK 41.5m rev. · NOK 775,000 profit

NORSK STANSEINDUSTRI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK STANSEINDUSTRI AS

Who owns NORSK STANSEINDUSTRI AS?

ECKMANN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NORSK STANSEINDUSTRI AS?

NORSK STANSEINDUSTRI AS had revenue of NOK 41.5m in 2025.

Who is the general manager of NORSK STANSEINDUSTRI AS?

Frode Daniel Bergheim is registered as general manager of NORSK STANSEINDUSTRI AS.

Where is NORSK STANSEINDUSTRI AS based?

NORSK STANSEINDUSTRI AS has its business address in Skedsmokorset.

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.