BIZTRAC BETA
Rental and operating of own or leased real estate

TOR AMUNDSEN AS

Org. no. 984590989 Limited company (AS) Rauma Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.8m
Equity NOK 1.4m
Incorporated 2002
Share capital NOK 409,000

TOR AMUNDSEN AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 984590989. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 409,000, divided into 100 shares. The company's stated purpose is: “Erverv, drift og utleie av fast eiendom, utleie av driftsutstyr samt alt som står i forbindelse med dette. Oppføring og rehabilitering av bygg samt alt som står i forbindelse med dette. Herunder deltakelse / investering i andre selskaper i tilsvarende bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.8m
Equity
NOK 1.4m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns TOR AMUNDSEN AS?

TOR AMUNDSEN
TOR AMUNDSEN AS
NOK 1.9m rev. · NOK 1.8m profit

TOR AMUNDSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOR AMUNDSEN AS

Who owns TOR AMUNDSEN AS?

TOR AMUNDSEN is the largest registered owner, with 100.0%.

What is the revenue of TOR AMUNDSEN AS?

TOR AMUNDSEN AS had revenue of NOK 1.9m in 2025.

Who is the general manager of TOR AMUNDSEN AS?

Tor Amundsen is registered as general manager of TOR AMUNDSEN AS.

Where is TOR AMUNDSEN AS based?

TOR AMUNDSEN AS has its business address in Åndalsnes.

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.