BIZTRAC BETA
Rental and operating of own or leased real estate

TORVESTNOR EIGEDOM AS

Org. no. 933173992 Limited company (AS) Kvam Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 202,000
Operating profit NOK 55,000
Equity NOK 252,000
Incorporated 2024
Share capital NOK 300,000

TORVESTNOR EIGEDOM AS is registered as a limited company in Kvam, Vestland with organisation number 933173992. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Kjøp, sal og utleige av fast eigedom og det som naturleg høyrer med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 202,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2024

Revenue
NOK 202,000
Operating profit
NOK 55,000
Equity
NOK 252,000
Est. value
NOK 266,000

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.0%
Weak
Equity as a share of total capital

Who owns TORVESTNOR EIGEDOM AS?

TORVESTNOR AS
TORVESTNOR EIGEDOM AS
NOK 202,000 rev. · NOK 55,000 profit

TORVESTNOR EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TORVESTNOR EIGEDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about TORVESTNOR EIGEDOM AS

Who owns TORVESTNOR EIGEDOM AS?

TORVESTNOR AS is the largest registered owner, with 100.0%.

What is the revenue of TORVESTNOR EIGEDOM AS?

TORVESTNOR EIGEDOM AS had revenue of NOK 202,000 in 2024.

Who is the general manager of TORVESTNOR EIGEDOM AS?

Torstein Vestrheim Norheim is registered as general manager of TORVESTNOR EIGEDOM AS.

Where is TORVESTNOR EIGEDOM AS based?

TORVESTNOR EIGEDOM AS has its business address in Øystese.

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.