BIZTRAC BETA
Photographic activities

BIRGITTE HORN FOTO AS

Org. no. 920444679 Limited company (AS) Voss Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 497,000
Operating profit NOK −1,000
Equity NOK 78,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

BIRGITTE HORN FOTO AS is registered as a limited company in Voss, Vestland with organisation number 920444679. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fotografvirksomhet, og det som natulig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 497,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 497,000
Operating profit
NOK −1,000
Equity
NOK 78,000
Est. value
NOK 560,000

Financial health · 2025

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.9%
Weak
Equity as a share of total capital

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

Who owns BIRGITTE HORN FOTO AS?

BIRGITTE HORN
BIRGITTE HORN FOTO AS
NOK 497,000 rev. · NOK −1,000 profit

BIRGITTE HORN FOTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRGITTE HORN FOTO AS

Who owns BIRGITTE HORN FOTO AS?

BIRGITTE HORN is the largest registered owner, with 100.0%.

What is the revenue of BIRGITTE HORN FOTO AS?

BIRGITTE HORN FOTO AS had revenue of NOK 497,000 in 2025.

Who is the general manager of BIRGITTE HORN FOTO AS?

Birgitte Horn is registered as general manager of BIRGITTE HORN FOTO AS.

Where is BIRGITTE HORN FOTO AS based?

BIRGITTE HORN FOTO AS has its business address in Voss.

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.