BIZTRAC BETA
Retail sale of other new goods

EROTIKK1 BERGEN AS

Org. no. 929552717 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −567,000
Equity NOK −1.5m
Incorporated 2022
Employees 17
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−567k kr).
  • Nylig endring 2026-06-10 Konkurs registrert 2026-06-10.

EROTIKK1 BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 929552717. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2022 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av produkter for erotisk helsepleie, veiledning og kurs, fotografi.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −567,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −567,000
Equity
NOK −1.5m

Financial health · 2024

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

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

Who owns EROTIKK1 BERGEN AS?

Malin Uglehus Unneland
EROTIKK1 BERGEN AS
NOK 2.1m rev. · NOK −567,000 profit

EROTIKK1 BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EROTIKK1 BERGEN AS

Who owns EROTIKK1 BERGEN AS?

Malin Uglehus Unneland is the largest registered owner, with 50.0%.

What is the revenue of EROTIKK1 BERGEN AS?

EROTIKK1 BERGEN AS had revenue of NOK 2.1m in 2024.

Where is EROTIKK1 BERGEN AS based?

EROTIKK1 BERGEN AS has its business address in Ulset.

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.