BIZTRAC BETA
Other technical consultancy

ANTISINK DRONE AS

Org. no. 928770966 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK −686,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−686k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ANTISINK DRONE AS is registered as a limited company in Kristiansand, Agder with organisation number 928770966. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby utstyr som bidrar til at droner som flyr over sjø og vann ikke synker eller forårsaker forsøpling, men kan hentes tilbake og avhendes på en forsvarlig måte. Dette er grønn teknologi som er gjenbrukbar og bærekraftig. I tillegg kan løsningen bidra til å sikre sensitiv data og bevare verdifulle eiendeler.”.

Key figures · 2024

Operating profit
NOK −28,000
Equity
NOK −686,000

Financial health · 2024

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

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

Who owns ANTISINK DRONE AS?

ANTISINK AS
ANTISINK DRONE AS
· NOK −28,000 profit

ANTISINK DRONE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANTISINK DRONE AS

Who owns ANTISINK DRONE AS?

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

Where is ANTISINK DRONE AS based?

ANTISINK DRONE AS has its business address in Kristiansand S.

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.