BIZTRAC BETA
Photographic activities

FOTOBO AS

Org. no. 915985645 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 381,000
Operating profit NOK 33,000
Equity NOK −32,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

FOTOBO AS is registered as a limited company in Stavanger, Rogaland with organisation number 915985645. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fotograftjenester og andre produkter/tjenester som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 381,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 381,000
Operating profit
NOK 33,000
Equity
NOK −32,000
Est. value
NOK 322,000

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-44.1%
Weak
Equity as a share of total capital

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

Who owns FOTOBO AS?

SEBASTIAAN FRANCISCUS BISSCHOP
FOTOBO AS
NOK 381,000 rev. · NOK 33,000 profit

FOTOBO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOTOBO AS

Who owns FOTOBO AS?

SEBASTIAAN FRANCISCUS BISSCHOP is the largest registered owner, with 100.0%.

What is the revenue of FOTOBO AS?

FOTOBO AS had revenue of NOK 381,000 in 2024.

Who is the general manager of FOTOBO AS?

Sebastiaan Franciscus Bisschop is registered as general manager of FOTOBO AS.

Where is FOTOBO AS based?

FOTOBO AS has its business address in Stavanger.

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.