BIZTRAC BETA
Manufacture of metal structures and parts of structures

ROST AS

Org. no. 990998582 Limited company (AS) Rennebu Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −62,000
Equity NOK 13.2m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

ROST AS is registered as a limited company in Rennebu, Trøndelag with organisation number 990998582. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive investeringsvirksomhet med aksjer og eiendom, samt utleie av driftsløsøre. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −62,000
Equity
NOK 13.2m
Est. value
NOK 15.5m

Financial health · 2025

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

Who owns ROST AS?

ROAR HAUGSET
ROST AS
NOK 0 rev. · NOK −62,000 profit

ROST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROST AS own?

ROST AS holds stakes in 8 companies:

See the full ownership structure →

Group structure

ROST AS er morselskap for 1 datterselskap:

Frequently asked questions about ROST AS

Who owns ROST AS?

ROAR HAUGSET is the largest registered owner, with 100.0%.

What is the revenue of ROST AS?

ROST AS had revenue of NOK 0 in 2025.

Who is the general manager of ROST AS?

Roar Haugset is registered as general manager of ROST AS.

Where is ROST AS based?

ROST AS has its business address in Rennebu.

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.