BIZTRAC BETA
Photographic activities

PREMIUM BOLIGFOTO AS

Org. no. 931084836 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 20,000
Equity NOK 114,000
Incorporated 2023
Share capital NOK 30,000

PREMIUM BOLIGFOTO AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931084836. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produsere film og foto av eiendom. Fotografering og visualisering av foto/film, webutvikling, grafisk utforming samt reklame- og portrettfotografering og alt som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 20,000
Equity
NOK 114,000
Est. value
NOK 139,000

Financial health · 2025

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

Who owns PREMIUM BOLIGFOTO AS?

AMIR PEDERSEN-PAYDAR
PREMIUM BOLIGFOTO AS
NOK 1.3m rev. · NOK 20,000 profit

PREMIUM BOLIGFOTO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PREMIUM BOLIGFOTO AS

Who owns PREMIUM BOLIGFOTO AS?

AMIR PEDERSEN-PAYDAR is the largest registered owner, with 50.0%.

What is the revenue of PREMIUM BOLIGFOTO AS?

PREMIUM BOLIGFOTO AS had revenue of NOK 1.3m in 2025.

Who is the general manager of PREMIUM BOLIGFOTO AS?

Amir Pedersen-Paydar is registered as general manager of PREMIUM BOLIGFOTO AS.

Where is PREMIUM BOLIGFOTO AS based?

PREMIUM BOLIGFOTO AS has its business address in Fredrikstad.

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.