biztrac. BETA
COMPANY REGISTER PROFILE
994933752 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ØVRE ROTVOLL AS

Org. no. 994933752 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 10.1m
Operating profit NOK 2.7m
Equity NOK 248.0m
Incorporated 2009
Share capital NOK 3.0m

ØVRE ROTVOLL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994933752. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 3.0m, divided into 10 shares. The company's stated purpose is: “Eie eiendommen Øvre Rotvoll gård og leie ut denne til landbruksformål og det som henger sammen med slik virksomhet, herunder forvaltning av kapital også etter et eventuelt utkjøp.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
▲ +22 %
Operating profit
NOK 2.7m
▲ +464 %
Equity
NOK 248.0m
▲ +2 %
Est. value
NOK 181.8m

Financial health · 2025

Liquidity
4.38
Very good
Current assets ÷ current liabilities
Profitability
3.9%
Weak
Return on total assets
Solidity
74.2%
Very good
Equity as a share of total capital

Who owns ØVRE ROTVOLL AS?

ØVRE ROTVOLL AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ØVRE ROTVOLL AS own?

ØVRE ROTVOLL AS holds stakes in 18 companies:

See the full ownership structure →

Frequently asked questions about ØVRE ROTVOLL AS

Who owns ØVRE ROTVOLL AS?

Ivar Oust is the largest registered owner, with 40.0%.

What is the revenue of ØVRE ROTVOLL AS?

ØVRE ROTVOLL AS had revenue of NOK 10.1m in 2025.

Where is ØVRE ROTVOLL AS based?

ØVRE ROTVOLL AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.