BIZTRAC BETA
Beverage serving activities

BOBA TEA AS

Org. no. 927906546 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −63,000
Equity NOK −290,000
Incorporated 2021
Employees 7
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−290k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−63k kr).

BOBA TEA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927906546. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2021 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Driver med cafebar for servering av mat, te og kaffe.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −63,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −63,000
Equity
NOK −290,000

Financial health · 2024

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

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

Who owns BOBA TEA AS?

ROBIN TRUNG TRAN
BOBA TEA AS
NOK 2.1m rev. · NOK −63,000 profit

BOBA TEA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOBA TEA AS

Who owns BOBA TEA AS?

ROBIN TRUNG TRAN is the largest registered owner, with 50.0%.

What is the revenue of BOBA TEA AS?

BOBA TEA AS had revenue of NOK 2.1m in 2024.

Who is the general manager of BOBA TEA AS?

My Lien Thi Tran is registered as general manager of BOBA TEA AS.

Where is BOBA TEA AS based?

BOBA TEA AS has its business address in Trondheim.

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.