BIZTRAC BETA
Repair and maintenance of electronic and optical equipment

DRONESPESIALISTEN AS

Org. no. 933537315 Limited company (AS) Fredrikstad Incorporated 2024 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

DRONESPESIALISTEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933537315. The business is classified under repair and maintenance of electronic and optical equipment (NACE 33.130). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Tilby reparasjonstjenester for droner. Vi fokuserer på å løse tekniske problemer og utføre nødvendig vedlikehold for å sikre at dronene fungerer optimalt.”.

Key figures

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns DRONESPESIALISTEN AS?

MUHARREM MEROVCI
DRONESPESIALISTEN AS
NOK 0 rev. · NOK 0 profit

DRONESPESIALISTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRONESPESIALISTEN AS

Who owns DRONESPESIALISTEN AS?

MUHARREM MEROVCI is the largest registered owner, with 100.0%.

What is the revenue of DRONESPESIALISTEN AS?

DRONESPESIALISTEN AS had revenue of NOK 0.

Who is the general manager of DRONESPESIALISTEN AS?

Muharrem Merovci is registered as general manager of DRONESPESIALISTEN AS.

Where is DRONESPESIALISTEN AS based?

DRONESPESIALISTEN AS has its business address in Torp.

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.