BIZTRAC BETA
Construction of residential and non-residential buildings

SNEKKERSERVICE STRØMSHEIM AS

Org. no. 925172669 Limited company (AS) Ålesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 57,000
Equity NOK 442,000
Incorporated 2020
Share capital NOK 30,000

SNEKKERSERVICE STRØMSHEIM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 925172669. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Monteringsarbeid og annen snekkervirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 57,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 57,000
Equity
NOK 442,000
Est. value
NOK 424,000

Financial health · 2024

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

Who owns SNEKKERSERVICE STRØMSHEIM AS?

RUNE STRØMSHEIM
SNEKKERSERVICE STRØMSHEIM AS
NOK 1.2m rev. · NOK 57,000 profit

SNEKKERSERVICE STRØMSHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNEKKERSERVICE STRØMSHEIM AS

Who owns SNEKKERSERVICE STRØMSHEIM AS?

RUNE STRØMSHEIM is the largest registered owner, with 100.0%.

What is the revenue of SNEKKERSERVICE STRØMSHEIM AS?

SNEKKERSERVICE STRØMSHEIM AS had revenue of NOK 1.2m in 2024.

Who is the general manager of SNEKKERSERVICE STRØMSHEIM AS?

Rune Strømsheim is registered as general manager of SNEKKERSERVICE STRØMSHEIM AS.

Where is SNEKKERSERVICE STRØMSHEIM AS based?

SNEKKERSERVICE STRØMSHEIM AS has its business address in Ålesund.

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.