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

SHOOTS AS

Org. no. 919316802 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 19.3m
Operating profit NOK −460,000
Equity NOK 781,000
Incorporated 2017
Employees 34
Share capital NOK 200,000

Signals

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

SHOOTS AS is registered as a limited company in Oslo, Oslo with organisation number 919316802. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2017 and has 34 registered employees. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Å produsere fotografi, video og annen visuell kommunikasjon, og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.3m in revenue and NOK −460,000 in operating profit.

Key figures · 2025

Revenue
NOK 19.3m
▼ −8 %
Operating profit
NOK −460,000
▼ −175 %
Equity
NOK 781,000
▼ −37 %
Est. value
NOK 20.6m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
-7.2%
Not satisfactory
Return on total assets
Solidity
22.7%
Good
Equity as a share of total capital

Who owns SHOOTS AS?

SHOOTS AS
NOK 19.3m rev. · NOK −460,000 profit

SHOOTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHOOTS AS

Who owns SHOOTS AS?

MAELSTROM AS is the largest registered owner, with 100.0%.

What is the revenue of SHOOTS AS?

SHOOTS AS had revenue of NOK 19.3m in 2025.

Who is the general manager of SHOOTS AS?

Christian Hvinden Melstrøm is registered as general manager of SHOOTS AS.

Where is SHOOTS AS based?

SHOOTS AS has its business address in Oslo.

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.