BIZTRAC BETA
Construction of residential and non-residential buildings

SØRMASKINERING AS

Org. no. 993786160 Limited company (AS) Kristiansand Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 26.7m
Operating profit NOK 1.5m
Equity NOK 5.5m
Incorporated 2009
Employees 10
Share capital NOK 100,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ØRMASKINERING AS is registered as a limited company in Kristiansand, Agder with organisation number 993786160. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2009 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg i stål samt det som naturlig står i forbindelse med dette, herunder deltakelse i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 26.7m
Operating profit
NOK 1.5m
Equity
NOK 5.5m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns SØRMASKINERING AS?

RAGO HOLDING AS
SØRMASKINERING AS
NOK 26.7m rev. · NOK 1.5m profit

SØRMASKINERING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRMASKINERING AS

Who owns SØRMASKINERING AS?

RAGO HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of SØRMASKINERING AS?

SØRMASKINERING AS had revenue of NOK 26.7m in 2024.

Where is SØRMASKINERING AS based?

SØRMASKINERING AS has its business address in Søgne.

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.