biztrac. BETA
COMPANY REGISTER PROFILE
988815004 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of employment placement agencies

ZAPP AS

Org. no. 988815004 Limited company (AS) Bamble Incorporated 2005 Active
Revenue 2025 NOK 0
Operating profit NOK −37,000
Equity NOK −478,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−478k kr).

ZAPP AS is registered as a limited company in Bamble, Telemark with organisation number 988815004. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsselskap både i aksjer og eiendom, utleie av eiendeler og arbeidskraft, import/eksport, salg av handelsvarer, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Former names: JAD AS

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −37,000
▼ −150 %
Equity
NOK −478,000
▼ −127 %
Est. value
NOK 129,000

Financial health · 2025

Liquidity
-611.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
42.6%
Very good
Return on total assets
Solidity
175.3%
Weak
Equity as a share of total capital

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

Who owns ZAPP AS?

ZAPP AS
NOK 0 rev. · NOK −37,000 profit

ZAPP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZAPP AS

Who owns ZAPP AS?

Jarle Atle Tande Dragsten is the largest registered owner, with 100.0%.

What is the revenue of ZAPP AS?

ZAPP AS had revenue of NOK 0 in 2025.

Where is ZAPP AS based?

ZAPP AS has its business address in Langesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.