BIZTRAC BETA
COMPANY REGISTER PROFILE
933613380 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

SUCCESSSERVE AS

Org. no. 933613380 Limited company (AS) Bamble Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 13,000
Incorporated 2024
Employees 7
Share capital NOK 38,000

Signals

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

SUCCESSSERVE AS is registered as a limited company in Bamble, Telemark with organisation number 933613380. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 38,000, divided into 375 shares. The company's stated purpose is: “Drive innen Kafe' og cateringvirksomhet og alt som naturlig hører sammen med slik virksomhet, herunder deltaking i andre selskap med lignende virksomhet. I tillegg skal selskapet drive innen transport og budtjenester.”.

Former names: WOODART AS

Key figures · 2024

Operating profit
NOK −17,000
Equity
NOK 13,000
Est. value
NOK 17,000

Financial health · 2024

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 SUCCESSSERVE AS?

OLEKSII STOROZHENKO
SUCCESSSERVE AS
· NOK −17,000 profit

SUCCESSSERVE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUCCESSSERVE AS

Who owns SUCCESSSERVE AS?

OLEKSII STOROZHENKO is the largest registered owner, with 80.0%.

Who is the general manager of SUCCESSSERVE AS?

Oleksii Storozhenko is registered as general manager of SUCCESSSERVE AS.

Where is SUCCESSSERVE AS based?

SUCCESSSERVE 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 15.06.2026.

Report a problem

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