BIZTRAC BETA
Joinery installation

SLS MONTASJE AS

Org. no. 991462252 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 95.1m
Operating profit NOK 15.2m
Equity NOK 14.6m
Incorporated 2007
Employees 25
Share capital NOK 73,000

Signals

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

SLS MONTASJE AS is registered as a limited company in Oslo, Oslo with organisation number 991462252. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2007 and has 25 registered employees. Registered share capital is NOK 73,000, divided into 726 shares. The company's stated purpose is: “Drive virksomhet i bygg og anlegg, og dertil tilhørende virksomhet. Selskapet kan ha eierinteresser i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 95.1m in revenue and NOK 15.2m in operating profit.

Key figures · 2024

Revenue
NOK 95.1m
Operating profit
NOK 15.2m
Equity
NOK 14.6m
Est. value
NOK 50.4m

Financial health · 2024

Liquidity
1.78
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.1%
Good
Equity as a share of total capital

Who owns SLS MONTASJE AS?

KMM INVEST AB
SLS MONTASJE AS
NOK 95.1m rev. · NOK 15.2m profit

SLS MONTASJE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLS MONTASJE AS

Who owns SLS MONTASJE AS?

KMM INVEST AB is the largest registered owner, with 81.8%.

What is the revenue of SLS MONTASJE AS?

SLS MONTASJE AS had revenue of NOK 95.1m in 2024.

Who is the general manager of SLS MONTASJE AS?

Karl Mikael Martinsson is registered as general manager of SLS MONTASJE AS.

Where is SLS MONTASJE AS based?

SLS MONTASJE AS has its business address in Oslo.

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.