BIZTRAC BETA
COMPANY REGISTER PROFILE
914074789 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Photographic activities

FOTOGRAF LYSTAD AS

Org. no. 914074789 Limited company (AS) Ørsta Incorporated 1972 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 426,000
Incorporated 1972
Share capital NOK 100,000

FOTOGRAF LYSTAD AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 914074789. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 1972. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Fotografisk arbeid og handel.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 426,000
Est. value
NOK 692,000

Financial health · 2025

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

Who owns FOTOGRAF LYSTAD AS?

FOTOGRAF LYSTAD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOTOGRAF LYSTAD AS

Who owns FOTOGRAF LYSTAD AS?

INGEBORG BHARATEE NILSEN LYSTAD is the largest registered owner, with 48.0%.

Who is the general manager of FOTOGRAF LYSTAD AS?

Per Ragnar Lystad is registered as general manager of FOTOGRAF LYSTAD AS.

Where is FOTOGRAF LYSTAD AS based?

FOTOGRAF LYSTAD AS has its business address in Ørsta.

Property

Business address Strandgata 2, 6150 Ørsta
Cadastral unit 1520-14/289/0/0
Building Kjøpesenter, varehus · 2 units

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.