biztrac. BETA
COMPANY REGISTER PROFILE
932575345 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other new goods

FOTO HOLDING AS

Org. no. 932575345 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 156.8m
Operating profit NOK 5.6m
Equity NOK 5.1m
Incorporated 2023
Employees 19
Share capital NOK 37,000

FOTO HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 932575345. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2023 and has 19 registered employees. Registered share capital is NOK 37,000, divided into 1000 shares. The company's stated purpose is: “Salg av fotoartikler og tjenester relatert til foto, samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 156.8m in revenue and NOK 5.6m in operating profit.

Key figures · 2025

Revenue
NOK 156.8m
▲ +1130 %
Operating profit
NOK 5.6m
▲ +2850 %
Equity
NOK 5.1m
▲ +19388 %
Est. value
NOK 14.1m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
18.7%
Very good
Return on total assets
Solidity
13.1%
Satisfactory
Equity as a share of total capital

Who owns FOTO HOLDING AS?

FOTO HOLDING AS
NOK 156.8m rev. · NOK 5.6m profit

FOTO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOTO HOLDING AS

Who owns FOTO HOLDING AS?

Sverre Monsen Sejersted is the largest registered owner, with 100.0%.

What is the revenue of FOTO HOLDING AS?

FOTO HOLDING AS had revenue of NOK 156.8m in 2025.

Who is the general manager of FOTO HOLDING AS?

Morten Wessel Nybrott is registered as general manager of FOTO HOLDING AS.

Where is FOTO HOLDING AS based?

FOTO HOLDING AS has its business address in Oslo.

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.