BIZTRAC BETA
Photographic activities

FOTOGRAF KIRSTI HOVDE AS

Org. no. 996467406 Limited company (AS) Lillehammer Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 38,000
Equity NOK 466,000
Incorporated 2011
Share capital NOK 100,000

FOTOGRAF KIRSTI HOVDE AS is registered as a limited company in Lillehammer, Innlandet with organisation number 996467406. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av varer og tjenester som fotograf. Konsulentvirksomhet innen fotograf faget, deltagelse i andre selskapet og virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 38,000
Equity
NOK 466,000
Est. value
NOK 466,000

Financial health · 2025

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

Who owns FOTOGRAF KIRSTI HOVDE AS?

KIRSTI HOVDE
FOTOGRAF KIRSTI HOVDE AS
NOK 1.1m rev. · NOK 38,000 profit

FOTOGRAF KIRSTI HOVDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOTOGRAF KIRSTI HOVDE AS

Who owns FOTOGRAF KIRSTI HOVDE AS?

KIRSTI HOVDE is the largest registered owner, with 100.0%.

What is the revenue of FOTOGRAF KIRSTI HOVDE AS?

FOTOGRAF KIRSTI HOVDE AS had revenue of NOK 1.1m in 2025.

Who is the general manager of FOTOGRAF KIRSTI HOVDE AS?

Kirsti Hovde is registered as general manager of FOTOGRAF KIRSTI HOVDE AS.

Where is FOTOGRAF KIRSTI HOVDE AS based?

FOTOGRAF KIRSTI HOVDE AS has its business address in Lillehammer.

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.