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

PIR I EIENDOM AS

Org. no. 920924182 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 20.2m
Operating profit NOK 9.6m
Equity NOK 74.3m
Incorporated 2018
Share capital NOK 60,000

PIR I EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 920924182. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 3000 shares. The company's stated purpose is: “Å eie og forvalte eiendommen i Keiser Wilhelmsgate 22, Gnr 201: Bnr 291 i Ålesund Kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.2m in revenue and NOK 9.6m in operating profit.

Former names: IDUNGÅRDEN AS

Key figures · 2025

Revenue
NOK 20.2m
▲ +5 %
Operating profit
NOK 9.6m
▲ +3 %
Equity
NOK 74.3m
▲ +3 %
Est. value
NOK 61.8m

Financial health · 2025

Liquidity
6.62
Very good
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
33.9%
Good
Equity as a share of total capital

Who owns PIR I EIENDOM AS?

PIR I EIENDOM AS
NOK 20.2m rev. · NOK 9.6m profit

PIR I EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIR I EIENDOM AS

Who owns PIR I EIENDOM AS?

PIR ÅLESUND AS is the largest registered owner, with 100.0%.

What is the revenue of PIR I EIENDOM AS?

PIR I EIENDOM AS had revenue of NOK 20.2m in 2025.

Who is the general manager of PIR I EIENDOM AS?

Anja Therese Rafteseth Solevågseide is registered as general manager of PIR I EIENDOM AS.

Where is PIR I EIENDOM AS based?

PIR I EIENDOM AS has its business address in Ålesund.

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.