BIZTRAC BETA
Motion picture, video and television programme production activities

AURLAND DRONESERVICE AS

Org. no. 929473299 Limited company (AS) Aurland Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 8,000
Operating profit NOK −6,000
Equity NOK −67,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−67k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

AURLAND DRONESERVICE AS is registered as a limited company in Aurland, Vestland with organisation number 929473299. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Dronetjenester og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 8,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 8,000
Operating profit
NOK −6,000
Equity
NOK −67,000

Financial health · 2024

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

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

Who owns AURLAND DRONESERVICE AS?

SIGVE VIKESLAND
AURLAND DRONESERVICE AS
NOK 8,000 rev. · NOK −6,000 profit

AURLAND DRONESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AURLAND DRONESERVICE AS

Who owns AURLAND DRONESERVICE AS?

SIGVE VIKESLAND is the largest registered owner, with 50.0%.

What is the revenue of AURLAND DRONESERVICE AS?

AURLAND DRONESERVICE AS had revenue of NOK 8,000 in 2024.

Where is AURLAND DRONESERVICE AS based?

AURLAND DRONESERVICE AS has its business address in Aurland.

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.