BIZTRAC BETA
COMPANY REGISTER PROFILE
932367068 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

CLASSIC EIENDOM AS

Org. no. 932367068 Limited company (AS) Rauma Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 96,000
Operating profit NOK 31,000
Equity NOK 528,000
Incorporated 1982
Share capital NOK 100,000

CLASSIC EIENDOM AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 932367068. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Utleie av fast eiendom og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 96,000 in revenue and NOK 31,000 in operating profit.

Former names: REITEN AS

Key figures · 2025

Revenue
NOK 96,000
▲ +0 %
Operating profit
NOK 31,000
▼ −33 %
Equity
NOK 528,000
▲ +0 %
Est. value
NOK 468,000

Financial health · 2025

Liquidity
7.47
Very good
Current assets ÷ current liabilities
Profitability
6.3%
Satisfactory
Return on total assets
Solidity
91.3%
Very good
Equity as a share of total capital

Who owns CLASSIC EIENDOM AS?

CLASSIC EIENDOM AS
NOK 96,000 rev. · NOK 31,000 profit

CLASSIC EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLASSIC EIENDOM AS

Who owns CLASSIC EIENDOM AS?

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

What is the revenue of CLASSIC EIENDOM AS?

CLASSIC EIENDOM AS had revenue of NOK 96,000 in 2025.

Who is the general manager of CLASSIC EIENDOM AS?

Hans Skiri is registered as general manager of CLASSIC EIENDOM AS.

Where is CLASSIC EIENDOM AS based?

CLASSIC EIENDOM 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 02.09.2026.

Report a problem

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