BIZTRAC BETA
Wholesale of machine tools

SMIUTSTYR AS

Org. no. 929529987 Limited company (AS) Askøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 951,000
Equity NOK 1.3m
Incorporated 2022
Share capital NOK 100,000

SMIUTSTYR AS is registered as a limited company in Askøy, Vestland with organisation number 929529987. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Import/eksport og salg av varer, foredling/bearbeiding av varer og materialer, kursvirksomhet, utleie av eiendom, kjøp og invistering av eiendom, aksjer og tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 951,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 951,000
Equity
NOK 1.3m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns SMIUTSTYR AS?

TORMOD HERSETH
SMIUTSTYR AS
NOK 2.8m rev. · NOK 951,000 profit

SMIUTSTYR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMIUTSTYR AS own?

SMIUTSTYR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMIUTSTYR AS

Who owns SMIUTSTYR AS?

TORMOD HERSETH is the largest registered owner, with 100.0%.

What is the revenue of SMIUTSTYR AS?

SMIUTSTYR AS had revenue of NOK 2.8m in 2025.

Who is the general manager of SMIUTSTYR AS?

Tormod Herseth is registered as general manager of SMIUTSTYR AS.

Where is SMIUTSTYR AS based?

SMIUTSTYR AS has its business address in Kleppestø.

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.