BIZTRAC BETA
Retail sale of other new goods

FOTO ERIK AS

Org. no. 980361128 Limited company (AS) Haugesund Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 10.6m
Operating profit NOK 2.0m
Equity NOK 1.5m
Incorporated 1998
Employees 5
Share capital NOK 100,000

FOTO ERIK AS is registered as a limited company in Haugesund, Rogaland with organisation number 980361128. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 1998 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Butikkdrift og annen handels- og tjenesteytende virksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.6m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 10.6m
Operating profit
NOK 2.0m
Equity
NOK 1.5m
Est. value
NOK 6.8m

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.7%
Good
Equity as a share of total capital

Who owns FOTO ERIK AS?

ENY HOLDING AS
FOTO ERIK AS
NOK 10.6m rev. · NOK 2.0m profit

FOTO ERIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FOTO ERIK AS own?

FOTO ERIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FOTO ERIK AS

Who owns FOTO ERIK AS?

ENY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FOTO ERIK AS?

FOTO ERIK AS had revenue of NOK 10.6m in 2024.

Who is the general manager of FOTO ERIK AS?

Eivind Nygaard is registered as general manager of FOTO ERIK AS.

Where is FOTO ERIK AS based?

FOTO ERIK AS has its business address in Haugesund.

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.