BIZTRAC BETA
Photographic activities

FOGRA REKLAMEFOTO AS

Org. no. 913571444 Limited company (AS) Sandefjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −37,000
Equity NOK 374,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−37k kr).

FOGRA REKLAMEFOTO AS is registered as a limited company in Sandefjord, Vestfold with organisation number 913571444. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reklamefotografering, fotografering, videofilm og hva herved står i forbindelse, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −37,000
Equity
NOK 374,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns FOGRA REKLAMEFOTO AS?

JON ERIK ANDERSEN
FOGRA REKLAMEFOTO AS
NOK 1.4m rev. · NOK −37,000 profit

FOGRA REKLAMEFOTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOGRA REKLAMEFOTO AS

Who owns FOGRA REKLAMEFOTO AS?

JON ERIK ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of FOGRA REKLAMEFOTO AS?

FOGRA REKLAMEFOTO AS had revenue of NOK 1.4m in 2024.

Who is the general manager of FOGRA REKLAMEFOTO AS?

Jon Erik Andersen is registered as general manager of FOGRA REKLAMEFOTO AS.

Where is FOGRA REKLAMEFOTO AS based?

FOGRA REKLAMEFOTO AS has its business address in Sandefjord.

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.