BIZTRAC BETA
Manufacture of soap and detergents, cleaning and polishing preparations

BEBEL FABRIKKER AS

Org. no. 910435167 Limited company (AS) Bergen Incorporated 1925 Active
Ownership graph ↗
Revenue 2025 NOK 648,000
Operating profit NOK −83,000
Equity NOK 126,000
Incorporated 1925
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).

BEBEL FABRIKKER AS is registered as a limited company in Bergen, Vestland with organisation number 910435167. The business is classified under manufacture of soap and detergents, cleaning and polishing preparations (NACE 20.410). The company was incorporated in 1925. Registered share capital is NOK 150,000. The company's stated purpose is: “Såpe- og teknisk kjemisk fabrikkvirksomhet og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 648,000 in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 648,000
Operating profit
NOK −83,000
Equity
NOK 126,000
Est. value
NOK 414,000

Financial health · 2025

Liquidity
52.21
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns BEBEL FABRIKKER AS?

ATLE SIGURD SVEEN
BEBEL FABRIKKER AS
NOK 648,000 rev. · NOK −83,000 profit

BEBEL FABRIKKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEBEL FABRIKKER AS

Who owns BEBEL FABRIKKER AS?

ATLE SIGURD SVEEN is the largest registered owner, with 70.0%.

What is the revenue of BEBEL FABRIKKER AS?

BEBEL FABRIKKER AS had revenue of NOK 648,000 in 2025.

Who is the general manager of BEBEL FABRIKKER AS?

Atle Sigurd Sveen is registered as general manager of BEBEL FABRIKKER AS.

Where is BEBEL FABRIKKER AS based?

BEBEL FABRIKKER AS has its business address in Espeland.

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.