BIZTRAC BETA
Manufacture of other special-purpose machinery n.e.c.

STANSEMAKEREN AS

Org. no. 937110286 Limited company (AS) Sarpsborg Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK 916,000
Equity NOK 2.5m
Incorporated 1984
Employees 14
Share capital NOK 100,000

STANSEMAKEREN AS is registered as a limited company in Sarpsborg, Østfold with organisation number 937110286. The business is classified under manufacture of other special-purpose machinery n.e.c. (NACE 28.990). The company was incorporated in 1984 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å utvikle, produsere og omsette stanseformer til emballasjeindustrien, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK 916,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK 916,000
Equity
NOK 2.5m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns STANSEMAKEREN AS?

TO - TUM AS
STANSEMAKEREN AS
NOK 12.5m rev. · NOK 916,000 profit

STANSEMAKEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STANSEMAKEREN AS

Who owns STANSEMAKEREN AS?

TO - TUM AS is the largest registered owner, with 100.0%.

What is the revenue of STANSEMAKEREN AS?

STANSEMAKEREN AS had revenue of NOK 12.5m in 2024.

Who is the general manager of STANSEMAKEREN AS?

Morten Ludvigsen is registered as general manager of STANSEMAKEREN AS.

Where is STANSEMAKEREN AS based?

STANSEMAKEREN AS has its business address in Borgenhaugen.

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.