BIZTRAC BETA
Retail sale of other new goods

FOTOHUSET JOHNSON AS

Org. no. 999589383 Limited company (AS) Bodø Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 12,000
Equity NOK 582,000
Incorporated 2013
Share capital NOK 30,000

FOTOHUSET JOHNSON AS is registered as a limited company in Bodø, Nordland with organisation number 999589383. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fotobutikk. Herunder all virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 12,000
Equity
NOK 582,000
Est. value
NOK 316,000

Financial health · 2025

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

Who owns FOTOHUSET JOHNSON AS?

ANDERS ESPOLIN JOHNSON
FOTOHUSET JOHNSON AS
NOK 3.6m rev. · NOK 12,000 profit

FOTOHUSET JOHNSON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FOTOHUSET JOHNSON AS own?

FOTOHUSET JOHNSON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FOTOHUSET JOHNSON AS

Who owns FOTOHUSET JOHNSON AS?

ANDERS ESPOLIN JOHNSON is the largest registered owner, with 100.0%.

What is the revenue of FOTOHUSET JOHNSON AS?

FOTOHUSET JOHNSON AS had revenue of NOK 3.6m in 2025.

Who is the general manager of FOTOHUSET JOHNSON AS?

Anders Espolin Johnson is registered as general manager of FOTOHUSET JOHNSON AS.

Where is FOTOHUSET JOHNSON AS based?

FOTOHUSET JOHNSON AS has its business address in Bodø.

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.