BIZTRAC BETA
Photographic activities

KARMØY FOTO AS

Org. no. 928533247 Limited company (AS) Karmøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −261,000
Equity NOK −322,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−322k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−261k kr).

KARMØY FOTO AS is registered as a limited company in Karmøy, Rogaland with organisation number 928533247. 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 300 shares. The company's stated purpose is: “Fotografering og portrettfotografering, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −261,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −261,000
Equity
NOK −322,000

Financial health · 2025

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

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

Who owns KARMØY FOTO AS?

LOVISE MANNES
KARMØY FOTO AS
NOK 1.1m rev. · NOK −261,000 profit

KARMØY FOTO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KARMØY FOTO AS

Who owns KARMØY FOTO AS?

LOVISE MANNES is the largest registered owner, with 50.0%.

What is the revenue of KARMØY FOTO AS?

KARMØY FOTO AS had revenue of NOK 1.1m in 2025.

Who is the general manager of KARMØY FOTO AS?

Ragna Marie Hereid is registered as general manager of KARMØY FOTO AS.

Where is KARMØY FOTO AS based?

KARMØY FOTO AS has its business address in Kvalavåg.

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.