BIZTRAC BETA
COMPANY REGISTER PROFILE
911985527 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Plumbing installation

SM RØRSERVICE AS

Org. no. 911985527 Limited company (AS) Ålesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 246,000
Operating profit NOK 8,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 30,000

SM RØRSERVICE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 911985527. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av VVS produkter og tjenester, og alt som hører naturlig under dette. Investering i eiendom, verdipapirer og andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 246,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 246,000
Operating profit
NOK 8,000
Equity
NOK 1.1m
Est. value
NOK 551,000

Financial health · 2025

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

Who owns SM RØRSERVICE AS?

STÅLE MYKLEBUST
SM RØRSERVICE AS
NOK 246,000 rev. · NOK 8,000 profit

SM RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SM RØRSERVICE AS

Who owns SM RØRSERVICE AS?

STÅLE MYKLEBUST is the largest registered owner, with 100.0%.

What is the revenue of SM RØRSERVICE AS?

SM RØRSERVICE AS had revenue of NOK 246,000 in 2025.

Who is the general manager of SM RØRSERVICE AS?

Ståle Myklebust is registered as general manager of SM RØRSERVICE AS.

Where is SM RØRSERVICE AS based?

SM RØRSERVICE 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.