BIZTRAC BETA
Photographic activities

BOTTEN PHOTOGRAPHY AS

Org. no. 983651372 Limited company (AS) Åmot Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 169,000
Operating profit NOK 37,000
Equity NOK −84,000
Incorporated 2001
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−84k kr).

BOTTEN PHOTOGRAPHY AS is registered as a limited company in Åmot, Innlandet with organisation number 983651372. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2001. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fotografering med dertil hørende salg av tjenester og kunst.”. The most recent filed accounts, for the 2025 financial year, show NOK 169,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 169,000
Operating profit
NOK 37,000
Equity
NOK −84,000
Est. value
NOK 254,000

Financial health · 2025

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-157.0%
Weak
Equity as a share of total capital

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

Who owns BOTTEN PHOTOGRAPHY AS?

LARS BOTTEN
BOTTEN PHOTOGRAPHY AS
NOK 169,000 rev. · NOK 37,000 profit

BOTTEN PHOTOGRAPHY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOTTEN PHOTOGRAPHY AS

Who owns BOTTEN PHOTOGRAPHY AS?

LARS BOTTEN is the largest registered owner, with 100.0%.

What is the revenue of BOTTEN PHOTOGRAPHY AS?

BOTTEN PHOTOGRAPHY AS had revenue of NOK 169,000 in 2025.

Who is the general manager of BOTTEN PHOTOGRAPHY AS?

Lars Botten is registered as general manager of BOTTEN PHOTOGRAPHY AS.

Where is BOTTEN PHOTOGRAPHY AS based?

BOTTEN PHOTOGRAPHY AS has its business address in Rena.

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.