BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

SØRMASKIN SWT AS

Org. no. 963957483 Limited company (AS) Kristiansand Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 51.1m
Operating profit NOK 3.1m
Equity NOK 2.0m
Incorporated 1992
Employees 13
Share capital NOK 569,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØRMASKIN SWT AS is registered as a limited company in Kristiansand, Agder with organisation number 963957483. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1992 and has 13 registered employees. Registered share capital is NOK 569,000, divided into 5686 shares. The company's stated purpose is: “Handel og hva hermed står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 51.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 51.1m
Operating profit
NOK 3.1m
Equity
NOK 2.0m
Est. value
NOK 13.0m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns SØRMASKIN SWT AS?

AHLSELL NORGE AS
SØRMASKIN SWT AS
NOK 51.1m rev. · NOK 3.1m profit

SØRMASKIN SWT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRMASKIN SWT AS

Who owns SØRMASKIN SWT AS?

AHLSELL NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of SØRMASKIN SWT AS?

SØRMASKIN SWT AS had revenue of NOK 51.1m in 2024.

Where is SØRMASKIN SWT AS based?

SØRMASKIN SWT AS has its business address in Kristiansand S.

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.