BIZTRAC BETA
Motion picture, video and television programme production activities

RAGGO DRONE AS

Org. no. 933037304 Limited company (AS) Tana Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 487,000
Operating profit NOK 229,000
Equity NOK 381,000
Incorporated 2024
Share capital NOK 30,000

RAGGO DRONE AS is registered as a limited company in Tana, Finnmark with organisation number 933037304. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby ulike dronetjenester. Dette vil være innenfor linje- og vindmølleinspeksjoner, produksjon av film og bilder, og eventuelt tjenester innenfor redningsaksjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 487,000 in revenue and NOK 229,000 in operating profit.

Key figures · 2025

Revenue
NOK 487,000
Operating profit
NOK 229,000
Equity
NOK 381,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
4.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.9%
Very good
Equity as a share of total capital

Who owns RAGGO DRONE AS?

NIILLAS STRENDO ANDERSEN
RAGGO DRONE AS
NOK 487,000 rev. · NOK 229,000 profit

RAGGO DRONE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAGGO DRONE AS

Who owns RAGGO DRONE AS?

NIILLAS STRENDO ANDERSEN is the largest registered owner, with 50.0%.

What is the revenue of RAGGO DRONE AS?

RAGGO DRONE AS had revenue of NOK 487,000 in 2025.

Who is the general manager of RAGGO DRONE AS?

Niillas Strendo Andersen is registered as general manager of RAGGO DRONE AS.

Where is RAGGO DRONE AS based?

RAGGO DRONE AS has its business address in Tana.

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.