biztrac. BETA
COMPANY REGISTER PROFILE
992841257 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Photographic activities

OSLO FOTO AS

Org. no. 992841257 Limited company (AS) Oslo Incorporated 2008 Active
Revenue 2025 NOK 18.6m
Operating profit NOK 3.2m
Equity NOK 2.0m
Incorporated 2008
Employees 17
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

OSLO FOTO AS is registered as a limited company in Oslo, Oslo with organisation number 992841257. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2008 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å drive salg av fotografiutstyr og fotografirelaterte produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.6m in revenue and NOK 3.2m in operating profit.

Former names: AKERSGATA FOTO AS, AKER FOTO AS

Key figures · 2025

Revenue
NOK 18.6m
▲ +8 %
Operating profit
NOK 3.2m
▲ +6 %
Equity
NOK 2.0m
▲ +36 %
Est. value
NOK 15.8m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns OSLO FOTO AS?

OSLO FOTO AS
NOK 18.6m rev. · NOK 3.2m profit

OSLO FOTO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLO FOTO AS

Who owns OSLO FOTO AS?

Marius Haugen is the largest registered owner, with 50.0%.

What is the revenue of OSLO FOTO AS?

OSLO FOTO AS had revenue of NOK 18.6m in 2025.

Who is the general manager of OSLO FOTO AS?

Hilde Furuseth Olivares is registered as general manager of OSLO FOTO AS.

Where is OSLO FOTO AS based?

OSLO FOTO 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.