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

SAPHOTOGRAPHY AS

Org. no. 922211531 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 192,000
Operating profit NOK −14,000
Equity NOK −277,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−277k kr).

SAPHOTOGRAPHY AS is registered as a limited company in Oslo, Oslo with organisation number 922211531. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Fotografvirksomhet, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 192,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 192,000
▼ −49 %
Operating profit
NOK −14,000
▲ +95 %
Equity
NOK −277,000
▼ −6 %

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
-47.1%
Not satisfactory
Return on total assets
Solidity
-871.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAPHOTOGRAPHY AS?

SAPHOTOGRAPHY AS
NOK 192,000 rev. · NOK −14,000 profit

SAPHOTOGRAPHY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAPHOTOGRAPHY AS

Who owns SAPHOTOGRAPHY AS?

Suleman Ahmad is the largest registered owner, with 100.0%.

What is the revenue of SAPHOTOGRAPHY AS?

SAPHOTOGRAPHY AS had revenue of NOK 192,000 in 2025.

Where is SAPHOTOGRAPHY AS based?

SAPHOTOGRAPHY 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.