BIZTRAC BETA
Rental and operating of own or leased real estate

BRINGSFJELLET PANORAMA AS

Org. no. 930115215 Limited company (AS) Lillehammer Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 569,000
Operating profit NOK 432,000
Equity NOK 2.9m
Incorporated 2022
Share capital NOK 348,000

BRINGSFJELLET PANORAMA AS is registered as a limited company in Lillehammer, Innlandet with organisation number 930115215. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 348,000, divided into 5004 shares. The company's stated purpose is: “Utleie av fritidsbolig og fast eiendom, forvaltning, utvikling, bygging og drift av eiendom, konsulenttjenester, investering i verdipapirer og fast eiendom, og det som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 569,000 in revenue and NOK 432,000 in operating profit.

Key figures · 2025

Revenue
NOK 569,000
Operating profit
NOK 432,000
Equity
NOK 2.9m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns BRINGSFJELLET PANORAMA AS?

PAMAS INVEST AS
BRINGSFJELLET PANORAMA AS
NOK 569,000 rev. · NOK 432,000 profit

BRINGSFJELLET PANORAMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRINGSFJELLET PANORAMA AS

Who owns BRINGSFJELLET PANORAMA AS?

PAMAS INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BRINGSFJELLET PANORAMA AS?

BRINGSFJELLET PANORAMA AS had revenue of NOK 569,000 in 2025.

Where is BRINGSFJELLET PANORAMA AS based?

BRINGSFJELLET PANORAMA AS has its business address in Lillehammer.

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.