BIZTRAC BETA
Repair and maintenance of household appliances and home and garden equipment

SM SERVICE & MONTERING AS

Org. no. 998490901 Limited company (AS) Eidsvoll Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 51,000
Equity NOK 606,000
Incorporated 2012
Share capital NOK 30,000

SM SERVICE & MONTERING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 998490901. The business is classified under repair and maintenance of household appliances and home and garden equipment (NACE 95.220). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å utføre reparasjoner av elektrisk utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 51,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 51,000
Equity
NOK 606,000
Est. value
NOK 537,000

Financial health · 2024

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

Who owns SM SERVICE & MONTERING AS?

STEINAR MYRVOLD
SM SERVICE & MONTERING AS
NOK 1.6m rev. · NOK 51,000 profit

SM SERVICE & MONTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SM SERVICE & MONTERING AS

Who owns SM SERVICE & MONTERING AS?

STEINAR MYRVOLD is the largest registered owner, with 100.0%.

What is the revenue of SM SERVICE & MONTERING AS?

SM SERVICE & MONTERING AS had revenue of NOK 1.6m in 2024.

Who is the general manager of SM SERVICE & MONTERING AS?

Steinar Myrvold is registered as general manager of SM SERVICE & MONTERING AS.

Where is SM SERVICE & MONTERING AS based?

SM SERVICE & MONTERING AS has its business address in Eidsvoll.

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.