BIZTRAC BETA
Photographic activities

SERVICE-DRONE AS

Org. no. 916085168 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −23,000
Equity NOK 204,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SERVICE-DRONE AS is registered as a limited company in Asker, Akershus with organisation number 916085168. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utføre foto/video oppdrag, samt andre tjenester som kan utføres med Multikopter (Drone). Utleie av kamera og utstyr til filmproduksjon. Og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −23,000
Equity
NOK 204,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns SERVICE-DRONE AS?

BRANCHES AS
SERVICE-DRONE AS
NOK 1.6m rev. · NOK −23,000 profit

SERVICE-DRONE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SERVICE-DRONE AS

Who owns SERVICE-DRONE AS?

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

What is the revenue of SERVICE-DRONE AS?

SERVICE-DRONE AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SERVICE-DRONE AS?

Stian Eivind Røyert Fjeldstad is registered as general manager of SERVICE-DRONE AS.

Where is SERVICE-DRONE AS based?

SERVICE-DRONE AS has its business address in Filtvet.

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.