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

TAMU SWAHILI FOOD AS

Org. no. 930074217 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 309,000
Operating profit NOK 15,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-12 Adresseendring registrert 2026-05-12.

TAMU SWAHILI FOOD AS is registered as a limited company in Oslo, Oslo with organisation number 930074217. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilbereding og salg av swahili matretter samt hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 309,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 309,000
Operating profit
NOK 15,000
Equity
NOK 15,000
Est. value
NOK 65,000

Financial health · 2024

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

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

Who owns TAMU SWAHILI FOOD AS?

TARMIYA HALIMA ABOOBAKER AWADH
TAMU SWAHILI FOOD AS
NOK 309,000 rev. · NOK 15,000 profit

TAMU SWAHILI FOOD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TAMU SWAHILI FOOD AS

Who owns TAMU SWAHILI FOOD AS?

TARMIYA HALIMA ABOOBAKER AWADH is the largest registered owner, with 25.0%.

What is the revenue of TAMU SWAHILI FOOD AS?

TAMU SWAHILI FOOD AS had revenue of NOK 309,000 in 2024.

Where is TAMU SWAHILI FOOD AS based?

TAMU SWAHILI FOOD AS has its business address in Oslo.

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.