BIZTRAC BETA
Photographic activities

FOTOGRAF KLAVESTAD AS

Org. no. 978687318 Limited company (AS) Lørenskog Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 216,000
Operating profit NOK 15,000
Equity NOK 53,000
Incorporated 1997
Share capital NOK 100,000

FOTOGRAF KLAVESTAD AS is registered as a limited company in Lørenskog, Akershus with organisation number 978687318. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Fotografvirksomhet ved hjelp av gamle og nye markedsføringstiltak. Samt annen virksomhet som er egnet til økonomisk vinning.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
Operating profit
NOK 15,000
Equity
NOK 53,000
Est. value
NOK 92,000

Financial health · 2025

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

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

Who owns FOTOGRAF KLAVESTAD AS?

HANS KLAVESTAD
FOTOGRAF KLAVESTAD AS
NOK 216,000 rev. · NOK 15,000 profit

FOTOGRAF KLAVESTAD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOTOGRAF KLAVESTAD AS

Who owns FOTOGRAF KLAVESTAD AS?

HANS KLAVESTAD is the largest registered owner, with 60.0%.

What is the revenue of FOTOGRAF KLAVESTAD AS?

FOTOGRAF KLAVESTAD AS had revenue of NOK 216,000 in 2025.

Who is the general manager of FOTOGRAF KLAVESTAD AS?

Hans Klavestad is registered as general manager of FOTOGRAF KLAVESTAD AS.

Where is FOTOGRAF KLAVESTAD AS based?

FOTOGRAF KLAVESTAD AS has its business address in Fjellhamar.

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.