BIZTRAC BETA
Repair and maintenance of machinery

STEIN RØSTAD AS

Org. no. 997723627 Limited company (AS) Oppdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 789,000
Equity NOK 1.6m
Incorporated 2011
Share capital NOK 180,000

STEIN RØSTAD AS is registered as a limited company in Oppdal, Trøndelag with organisation number 997723627. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2011. Registered share capital is NOK 180,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter, å eie og drive fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 789,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 789,000
Equity
NOK 1.6m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns STEIN RØSTAD AS?

ROGER RØSTAD HOLDING AS
STEIN RØSTAD AS
NOK 1.1m rev. · NOK 789,000 profit

STEIN RØSTAD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STEIN RØSTAD AS own?

STEIN RØSTAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEIN RØSTAD AS

Who owns STEIN RØSTAD AS?

ROGER RØSTAD HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of STEIN RØSTAD AS?

STEIN RØSTAD AS had revenue of NOK 1.1m in 2024.

Who is the general manager of STEIN RØSTAD AS?

Stein Røstad is registered as general manager of STEIN RØSTAD AS.

Where is STEIN RØSTAD AS based?

STEIN RØSTAD AS has its business address in Oppdal.

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.