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

YRJAR PANORAMA AS

Org. no. 913945522 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 74.5m
Operating profit NOK 72.5m
Equity NOK 621,000
Incorporated 2014
Share capital NOK 400,000

YRJAR PANORAMA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913945522. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging, drift og utleie av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.5m in revenue and NOK 72.5m in operating profit.

Key figures · 2025

Revenue
NOK 74.5m
▲ +1660 %
Operating profit
NOK 72.5m
▲ +2704 %
Equity
NOK 621,000
▲ +55 %
Est. value
NOK 92.4m

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
149.2%
Very good
Return on total assets
Solidity
0.8%
Not satisfactory
Equity as a share of total capital

Who owns YRJAR PANORAMA AS?

YRJAR PANORAMA AS
NOK 74.5m rev. · NOK 72.5m profit

YRJAR PANORAMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YRJAR PANORAMA AS

Who owns YRJAR PANORAMA AS?

AHA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of YRJAR PANORAMA AS?

YRJAR PANORAMA AS had revenue of NOK 74.5m in 2025.

Where is YRJAR PANORAMA AS based?

YRJAR PANORAMA 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.