biztrac. BETA
COMPANY REGISTER PROFILE
929186249 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Manufacture of locks and hinges

STANTEK AS

Org. no. 929186249 Limited company (AS) Kongsvinger Incorporated 1978 Active
Ownership graph ↗
Revenue 2025 NOK 41.6m
Operating profit NOK 737,000
Equity NOK 9.8m
Incorporated 1978
Employees 18
Share capital NOK 2.5m

STANTEK AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 929186249. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 1978 and has 18 registered employees. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Mekanisk verksteddrift samt hva hermed står i forbindelse, - herunder delta i andre selskaper med liknende eller beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 41.6m in revenue and NOK 737,000 in operating profit.

Former names: Stantek Kongsvinger A/S

Key figures · 2025

Revenue
NOK 41.6m
▲ +17 %
Operating profit
NOK 737,000
▲ +74 %
Equity
NOK 9.8m
▲ +27 %
Est. value
NOK 6.9m

Financial health · 2025

Liquidity
1.69
Good
Current assets ÷ current liabilities
Profitability
3.7%
Weak
Return on total assets
Solidity
38.0%
Good
Equity as a share of total capital

Who owns STANTEK AS?

STANTEK AS
NOK 41.6m rev. · NOK 737,000 profit

STANTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STANTEK AS

Who owns STANTEK AS?

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

What is the revenue of STANTEK AS?

STANTEK AS had revenue of NOK 41.6m in 2025.

Who is the general manager of STANTEK AS?

Terje Sunnanå Aalrust is registered as general manager of STANTEK AS.

Where is STANTEK AS based?

STANTEK AS has its business address in Kongsvinger.

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

Report a problem

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