BIZTRAC BETA
COMPANY REGISTER PROFILE
934438175 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

SOM-SAMBUSA AS

Org. no. 934438175 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 21,000
Operating profit NOK −13,000
Equity NOK 5,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SOM-SAMBUSA AS is registered as a limited company in Bergen, Vestland with organisation number 934438175. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen restaurantdrift - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 21,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

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

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.2%
Weak
Equity as a share of total capital

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

Who owns SOM-SAMBUSA AS?

NAIMO MAHMUD SIDOW
SOM-SAMBUSA AS
NOK 21,000 rev. · NOK −13,000 profit

SOM-SAMBUSA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOM-SAMBUSA AS

Who owns SOM-SAMBUSA AS?

NAIMO MAHMUD SIDOW is the largest registered owner, with 33.3%.

What is the revenue of SOM-SAMBUSA AS?

SOM-SAMBUSA AS had revenue of NOK 21,000 in 2025.

Where is SOM-SAMBUSA AS based?

SOM-SAMBUSA AS has its business address in Bergen.

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.