BIZTRAC BETA
Site preparation

ROAR ØVERDAL AS

Org. no. 930685321 Limited company (AS) Åfjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 678,000
Operating profit NOK 183,000
Equity NOK 295,000
Incorporated 2023
Share capital NOK 40,000

ROAR ØVERDAL AS is registered as a limited company in Åfjord, Trøndelag with organisation number 930685321. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Utleie av maskiner, landbrukstjenester og konsulenttjenester og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 678,000 in revenue and NOK 183,000 in operating profit.

Key figures · 2025

Revenue
NOK 678,000
Operating profit
NOK 183,000
Equity
NOK 295,000
Est. value
NOK 699,000

Financial health · 2025

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

Who owns ROAR ØVERDAL AS?

LISBETH SNEVE ØVERDAL
ROAR ØVERDAL AS
NOK 678,000 rev. · NOK 183,000 profit

ROAR ØVERDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROAR ØVERDAL AS

Who owns ROAR ØVERDAL AS?

LISBETH SNEVE ØVERDAL is the largest registered owner, with 50.0%.

What is the revenue of ROAR ØVERDAL AS?

ROAR ØVERDAL AS had revenue of NOK 678,000 in 2025.

Who is the general manager of ROAR ØVERDAL AS?

Roar Øverdal is registered as general manager of ROAR ØVERDAL AS.

Where is ROAR ØVERDAL AS based?

ROAR ØVERDAL AS has its business address in Brandsfjord.

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.