BIZTRAC BETA
Photographic activities

RESVIK FOTO AS

Org. no. 930013781 Limited company (AS) Grimstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 753,000
Operating profit NOK 86,000
Equity NOK 131,000
Incorporated 2022
Share capital NOK 30,000

RESVIK FOTO AS is registered as a limited company in Grimstad, Agder with organisation number 930013781. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal selge tjenester og varer innen Foto. Fotografering av nyfødt, barn, konfirmanter, bryllup, etc. Deretter salg av print/album, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 753,000 in revenue and NOK 86,000 in operating profit.

Key figures · 2025

Revenue
NOK 753,000
Operating profit
NOK 86,000
Equity
NOK 131,000
Est. value
NOK 496,000

Financial health · 2025

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

Who owns RESVIK FOTO AS?

SIW MERETE VERDAL RESVIK
RESVIK FOTO AS
NOK 753,000 rev. · NOK 86,000 profit

RESVIK FOTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESVIK FOTO AS

Who owns RESVIK FOTO AS?

SIW MERETE VERDAL RESVIK is the largest registered owner, with 100.0%.

What is the revenue of RESVIK FOTO AS?

RESVIK FOTO AS had revenue of NOK 753,000 in 2025.

Who is the general manager of RESVIK FOTO AS?

Siw Merete Verdal Resvik is registered as general manager of RESVIK FOTO AS.

Where is RESVIK FOTO AS based?

RESVIK FOTO AS has its business address in Grimstad.

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.