BIZTRAC BETA
Manufacture of other plastic products

DROPTAG AS

Org. no. 933242110 Limited company (AS) Skien Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 83,000
Operating profit NOK −3,000
Equity NOK 21,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

DROPTAG AS is registered as a limited company in Skien, Telemark with organisation number 933242110. The business is classified under manufacture of other plastic products (NACE 22.260). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Produksjon og salg av bærekraftige produkter, inkludert utvikling, markedsføring og distribusjon av miljøvennlige løsninger og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 83,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 83,000
Operating profit
NOK −3,000
Equity
NOK 21,000
Est. value
NOK 56,000

Financial health · 2024

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

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

Who owns DROPTAG AS?

SANDER LANGELAND ØVERBØ
DROPTAG AS
NOK 83,000 rev. · NOK −3,000 profit

DROPTAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DROPTAG AS

Who owns DROPTAG AS?

SANDER LANGELAND ØVERBØ is the largest registered owner, with 33.3%.

What is the revenue of DROPTAG AS?

DROPTAG AS had revenue of NOK 83,000 in 2024.

Who is the general manager of DROPTAG AS?

Sander Langeland Øverbø is registered as general manager of DROPTAG AS.

Where is DROPTAG AS based?

DROPTAG AS has its business address in Skien.

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.